When looking for fastest DataView grid i have noticing pidog solution as einhugur solution is only for old realbasic?.
I think if i am not mistaken it’s been two times i have encountered such issues.
I have reported few hours ago in here <https://xojo.com/issue/54495>. Perhaps you could take a look and see if it’s crashes in some of your machine?, Only need to open “dataview1.13.3.xojo_binary_project” project, setting the architecture and run the project.
The “EddiesElectronics” example is compiled fine for x64 Windows binary. As pidog DataView grid is encrypted unless you get the source, perhaps that’s should pin point it?, somehow Xojo compiler mismatch something in the process of compilation?.
Why i am more believe on Xojo bugs on compiler or linker are i have more narrowing it down into baremetal Windows installation without anything extra in it and yet it still failed. From searching on feedback cases i can see only around 3 people including me who has these matter.
The wisest solution would be remote debug or support but it’s out my league for Xojo reimbursement.
Been long day for me, sleepless night in thinking that’s a hardware problem.
An old favourite is ‘Turn off your anti-virus software and try XYZ’. Never been my favourite, but when you are short of options maybe it’s worth a shot.
Any automated backup software running? If so, try turning that off as well.
I don’t think you mention it anywhere, but are you able to Run your project?
There is some IDE logging information that can be viewed with third party tools.
By far the most common is DebugView: https://docs.microsoft.com/en-us/sysinternals/downloads/debugview
I have no idea if it will show anything useful for this issue, but again, when short on options it’s worth a shot.
[quote=418757:@Robin Lauryssen-Mitchell]Hi Aditya,
What are the other three case numbers?
An old favourite is ‘Turn off your anti-virus software and try XYZ’. Never been my favourite, but when you are short of options maybe it’s worth a shot.
Any automated backup software running? If so, try turning that off as well.
I don’t think you mention it anywhere, but are you able to Run your project?
Unfortunately I am out for most of tomorrow.[/quote] #51989 , mine, and if i am not mistaken one more that i have found when searching on feedback.
Please read my reply above, already done it, there is no 3rd party antivirus installed apart than only plain windows defender, already tried to disable, adding xojo installation folder into windows defender exclusion list, and adding temporary folder also into exclusion list. Tried also adding xojo.exe, lld exe with turned off all of anti exploit in windows defender.
Already tried debug view running it as administrator but there are no ‘interesting’ stuff being logged :
Administrator command prompt resulting the same error.
Normal user command prompt resulting the same error.
Also tried :
Moving out temporary windows folder (%TEMP & %TMP% env variables) into other drives which are :
Mechanical HDD Drive connected through Sata 6G connection into the motherboard, the same thing.
Mechanical HDD Drive connected through an external enclosure into USB 3.0, the same thing
Changing my region from English - Indonesia into English U.S with the same result
Modified some of my bios settings to look for any wrongly setup bios settings
The strange thing is for the aforementioned example project, it’s probably the only example project that is ‘incompatible’ with my workstation.
If it’s because of Windows or hardware failures, why :
Other examples project managed to build into x64 Windows binaries.
The Xojo error log is remain consistence about failure to compile between Windows 10 x64 1803 (RS4), 1809(RS5) and RS6 (Prerelease)
Moving out windows’s temporary folder to other drives will work if my SSD is failing.
Untouched plain clean Windows installation will works.
Memory test passed
Able to play AAA games
Able to compile Non-Xojo large project such as QT 5.12
Not experiencing any Windows BSOD, GSOD
@Greg O’Lone
Thanks Greg for joining in, it’s been three days already, i hope you will able to track down the causes.
It’s one line error, when i am right clicking in the error and choosing copy then it’s being expanded in the clipboard or when pasting it into a text editor.
The screenshot :
Addition, when searching in Windows event viewer, i could not found anything of “lld.exe” or “xojo.exe” related entries.
[quote=418838:@Aditya Nugraha]Nothing too because of perhaps Xojo is GUI application rather than Windows console application? [/quote]
Not necessarily. The IDE does write some warning messages to stdout from time to time. Usually they are harmless, but sometimes will shed some light in a difficult problem.
Hi Aditya,
I realise that closing the Feedback case is going be upsetting. But we really cannot provide hardware and/or operating system support beyond “It might be XYZ, try ABC”. In addition you have mentioned that you have been able to build your project successfully on other machines. This really does look like an issue specific to that one machine.
@
I don’t overclocking my CPU, only default settings from the bios about CPU performance. Currently my CPU running at stock/default clock which is 2.59 GHz.
My storage itself is not the form of SATA, but it’s a PCIe NVMe - M.2, i have closing the theory of my storage being the issue because of i was already tried booting into a windows 10 x64 1809 pro inside a mechanical 2.5" notebook hard drive within HDD external enclosure in which connected through a USB into the motherboard and yet it still failed.
Also have tried to disable Meltdown & spectre mitigation from windows (confirmed disabled by the inspectre application), and yet still failed unless i am disabled Hyper-Threading for the CPU from within the bios.
I think this will be a chicken egg thing , all side (Intel, Microsoft, Xojo) will be able to provide somekind of work-around about these matter.
I have tried to logged this issue into Microsoft feedback app, for some weird reason it’s not being logged, i couldn’t found the reported issue in my issue part of the feddback app, it’s just like i don’t report anything.
Because of i don’t have any private channel into either Microsoft, Intel or Asus, it will be long and tedious process to report it from the beginning again, i was tried to contact Asus Indonesia, instead of understanding the issue, the supports only doing scripted replies and blaming it on customer, or straight into RMA process.
I am sure that with Xojo credibility, at-least one or more of Xojo’s engineer team is having those private line/channel into aforementioned companies.
I am really hoping for Xojo to taking the good will and make some kind of workaround in their compiler/linker code for this matter.
It’s not my choosing of my problematic case for happening at really not choice-able timeframe (holiday, end of the year).
Just found out Xojo compiler has failed to compiling Bkeeney’s Chinook ARGen Example which my work quite un-usable. The error about Chinook ARGen Example is :
[quote]Linking Executable
C:\Program Files\Xojo\Xojo 2018r4\Xojo Resources\Win32\lld.exe: error: C:\Users\echelon\AppData\Local\Temp\xojo scratch 6924\ChinookARGen [974F2B33]\Windows_x86_64\/Data.o: The file was not recognized as a valid object file[/quote]
which my work quite un-usable. The error about Chinook ARGen Example is :