Sometimes I’m getting a crash with the following info:
any clue about what is wrong in my code?
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.xojo.XojoFramework 0x000000010822f365 RuntimeObjectIsa + 80
1 com.xojo.XojoFramework 0x00000001082418ef RuntimeViewDestructor + 139
2 com.enric.TRC 0x000000010793dc1b Window.__Exit%%o + 11
3 com.xojo.XojoFramework 0x000000010822f13b RuntimeUnlockObject + 643
4 com.enric.TRC 0x0000000107b88c1e GameMotion.StartBattleResolution + 270
5 com.enric.TRC 0x0000000107b856f4 GameMotion.StartFase + 1060
…
That’s really nothing to go on. You’ll need to post the few lines above these lines in the crash report that show the actual reason.
opps, I trowed them away. I think I may revover in Library/some_I_Do_not_remember
Found
Process: TRC [1617]
Path: /Users/USER/Documents/*/TRC.app/Contents/MacOS/TRC
Identifier: com.enric.TRC
Version: 1.0 [6] (1.0.0.0.7)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: TRC [1617]
User ID: 502
Date/Time: 2022-01-05 12:19:59.665 +0100
OS Version: Mac OS X 10.14.6 (18G8022)
Report Version: 12
Anonymous UUID: DBEDDFEF-DFAC-B603-69BC-B2B282ED22C1
Sleep/Wake UUID: D42CFF8C-40B4-4A2C-A4B9-74E252C8BD95
Time Awake Since Boot: 9200 seconds
Time Since Wake: 160 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 0x0000000000000008
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1617]
VM Regions Near 0x8:
→
__TEXT 00000001078d2000-0000000107dd2000 [ 5120K] r-x/r-x SM=COW /Users/USER/Documents/*/TRC.app/Contents/MacOS/TRC
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.xojo.XojoFramework 0x000000010822f365 RuntimeObjectIsa + 80
1 com.xojo.XojoFramework 0x00000001082418ef RuntimeViewDestructor + 139
2 com.enric.TRC 0x000000010793dc1b Window.__Exit%%o + 11
3 com.xojo.XojoFramework 0x000000010822f13b RuntimeUnlockObject + 643
4 com.enric.TRC 0x0000000107b88c1e GameMotion.StartBattleResolution + 270
Do a search for RuntimeUnlockObject in the forum. AFAIR the crash comes from accessing controls that already have been destroyed.
I think, in my case, I will avoid this RuntimeUnlockObject changing a call from a close window even to another place.
May be related, feedback #67013 - this one is on Windows. I just added information for a crash that just happened to me.
Check to see if your app is running out of RAM. A lot of segmentation faults that we encounter are just that.
How does modern App run out of Ram ?? There really is no such thing, App runs in 64bit pot and swaps to disk if you run out of physical ram.
Using up a lot of ram can though increase risk of hitting a problem if the App is leaking or buggy by writing in invalid memory addresses. But of course then its just identifying that there are buggy bits in the framework.
2 Likes
You’re assuming that the machine has adequate memory and disk space to accommodate all of the running processes, but we see this all the time on Linux servers that are sometimes running low on both and the system log clearly states that it ran out of RAM. It’s worth looking into if just to find out if the app was reported as having used 176GB of RAM just before it crashed or something like that.