I’m having trouble isolating the cause of this crash. I’m running Xojo 2025 v3.0. When I test the hosted version of the app vs. the identical version running in the IDE, the hosted version works fine while the IDE crashes. One difference is that I’m using MySQL as the dbase in my local environment, and MariaDB in Xojo Cloud. Any advice on what an “access violation” is would be greatly appreciated!
Rolling the project back to Xojo 2025 r2.1 has eliminated the issue, but I’d still like to understand what this bug in r3.0 is, and if I can resolve it and continue updating my projects.
Build the app and let it crash so you get a crash report.
This is probably an invalid pointer.
Like access on an object that is already freed.
Where do the crash reports get saved (dumped) to? Thanks for you reply @Christian_Schmitz
On macOS usually into the ~/Library/Logs/DiagnosticReports folder.
This is interesting. We have rolled back from Xojo2025R3 to Xojo2025R2.1 because the Xojo2025R3 seems to be unstable. We don’t know the reason just yet, still trying to get more info, but definitely your posting caught my eye. Thanks for sharing.