I have been sent this error message from a customer who cannot speak English, and from whom I cannot get a lot of actual information about what was being done at the time.
Is there anything in this message to suggest why my app might be crashing for them?
(This is not reported by others. The machine is running in French. I’m guessing its an intel machine, as the app is UB)
X86-64 (Translated)
launchd
[1]
501
Date/Time:
OS Version:
Report Version:
Anonymous UUID:
2024-02-20 21:15:20.0162 +0100
macOS 14.2.1 (23C71)
390518D8-5587-3EC1-CF30-2B55AD01AA79
Sleep/Wake UUID:
726FD479-1E8F-4BA2-969D-1FDAC6D652B4
Time Awake Since Boot: 7100 seconds
Time Since Wake:
1312 seconds
System Integrity Protection: enabled
Notes:
PC register does not match crashing frame (0x0 vs 0x10687B730)
Crashed Thread:
0 Dispatch queue: com apple-main-thread
ExceptionType:
Exception Codes:
Exception Codes:
Termination Reason:
Terminating Process:
EXC
_BAD_ACCESS (SIGSEGV)
KERN_INVALID_ADDRESS at Oxffae00aaff8200fc → 0xffff80aff8200fc (possible pointer authentication failure)
0x0000000000000001, Oxffae00aff8200fc
Namespace SIGNAL, Code 11 Segmentation fault: 11
exc handler [1284]
VM Region Info: 0xffff80aff8200c is not in any region.
Bytes after previous region: 18446463346918408445
TYPICAL REGION
START - END
I VSIZE] PRT/MAX SHRMOD
REGION DETAIL
mapped file
7ffca38a000-7ffccc24000 [650. 1M] rx/rx SM=COW … t_id=c55b9435
UNUSED SPACE AT END
Error Formulating Crash Report:
PC register does not match crashing frame (0x0 vs 0x10687B730)
I found some results when goggling this sentence but nothing conclusive. Can the user send the full crash log?
1 Like
Maybe accessing a Niled object or something like that… (sending a message or calling a function on a non-existent / valid object at the address pointed by the reference)
Hard to tell without additional info…
1 Like
Can the user send the full crash log?
So far, they cannot tell me which menu item they used, or the version number on the help/about dialog.
I’ll persevere.
This is from a Intel app running on Apple Silicon.
SIGSEGV basically means invalid pointer, you have something addressing a memory location that either no longer exists or it is outside of your memory space.
Yup, invalid memory address.
This one is a deal breaker. Without a stack trace you can’t identify if its from Apple API, Xojo framework or your own code.
There is a possibility… That this might be due to a conflict between the OS relaunching the application after a restart. Recently Apple created a new app state for re-launched apps, where it makes the customer think the app has relaunched, but to save memory… It hasn’t really. It may be that Xojo needs to update their Mac framework to support this (Good luck in that happening).
His Mac was rebooted two hours before the crash, and had been “Awake” for 21 minutes, was your application running the entire time, I can’t say.
I would suggest the customer downloads a new copy of the application from your site, this way you ensure that it’s the latest and you decrease the chance that the customer enables the run in Rosetta option.
Thanks Sam. Good to have some things to try
This is from a Intel app running on Apple Silicon.
Yes, I thought that was odd.
1 Like