I think there are one or two exceptions to that but they are calling into plugins and those cant always be caught
But if its just your code I cant think of anything that cant be
So this seems to have crept back up from a user. I am getting reports about a crash at seemingly random times in an app (Not associated with closing an event, or even an action per say, the app can be sitting open and crash). The app in question was built using 2019r1.
Process: XXX  Path: XXX Identifier: XXX Version: 13.9.2 (184.108.40.206.62) Code Type: X86-64 (Native) Parent Process: ???  Responsible: XXX  User ID: 501 Date/Time: 2019-05-17 09:02:41.967 -0600 OS Version: Mac OS X 10.11.6 (15G31) Report Version: 11 Anonymous UUID: 3D2599F9-DCD6-89C2-E31D-D5FA0FBEA997 Sleep/Wake UUID: 3D7BF9AF-95B8-4DE1-B173-E63F72F39BF0 Time Awake Since Boot: 610000 seconds Time Since Wake: 7400 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0x20: --> __TEXT 0000000107de5000-000000010cdb7000 [ 79.8M] r-x/rwx SM=COW XXX Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00007fff91ad416f objc_release + 31 1 com.apple.CoreFoundation 0x00007fff9bacdc12 _CFAutoreleasePoolPop + 50 2 com.apple.Foundation 0x00007fff97ce79ea -[NSAutoreleasePool drain] + 153 3 com.apple.AppKit 0x00007fff8bd50e53 -[NSApplication run] + 893 4 com.xojo.XojoFramework 0x000000010db4384d RuntimeRun + 42 5 com.desertsandsoft.smartoutfitter 0x0000000107f605a3 REALbasic._RuntimeRun + 19 6 com.desertsandsoft.smartoutfitter 0x000000010c975ce8 _Main + 536 7 com.desertsandsoft.smartoutfitter 0x000000010c96cc63 main + 19 8 libdyld.dylib 0x00007fff9ad955ad start + 1
Another framework bug?
The app continues to crash at random times, some of the crash reports have this message:
*** error for object 0x7fb6aeb6b350: incorrect checksum for freed object - object was probably modified after being freed.
It seems like these crashes are linked to the machine running OSX 10.11.6.
This same piece of software runs on other machines running newer versions that do not produce this behavior. Does Xojo have known reverse compatibility issues?