I had a hard crash on an app created under Xojo yesterday after the app was running for almost an hour without no problem. As it was continuing to do exactly the same thing with no human intervention, it crashed. When I saw that, I started it again, and had it do exactly the same work again, and this time it finished the job without any problem.
I got the following crash report:
OS Version: Mac OS X 10.10.5 (14F2511)
Time Awake Since Boot: 240000 seconds
Time Since Wake: 8700 seconds
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
–>
__TEXT 0000000000001000-00000000002df000 [ 2936K] r-x/rwx SM=COW /Users/USER/Desktop/Time To Run II.app/Contents/MacOS/Time To Run II
From reading other posts in his forum I understand that EXC_BAD_ACCESS means that the computer tried to access a part of memory that was no longer available but I cannot understand why.
Also isn’t it strange that round number for Time Awake, although probably this has nothing to do with the problem?
Thank you for first answers. Here is more of the log. The app was compiles in an older version of Xoxo (2013r3) so it should be well under line with OS 10.
That soft monitors/controls a physical machine in a photographic darkroom (screen killed with ctrl-caps-eject!), serial communicating through USB with an Arduino.
Here it came up again; I’ve had the same crash today, again in the middle of nowhere after an hour or so of running the program.
Does anyone has an understanding of what is going on so that I can try to find a solution?
Thank you
Nicolas
Date/Time: 2020-11-09 14:50:06.007 +0100
OS Version: Mac OS X 10.10.5 (14F2511)
Report Version: 11
Anonymous UUID: A7770072-CF00-632F-DFD1-EFEBC6287E34
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
–>
__TEXT 0000000000001000-00000000002e3000 [ 2952K] r-x/rwx SM=COW /Users/USER/Desktop/Time To Run II.app/Contents/MacOS/Time To Run II
I ran the same one-hour-plus long procedure again, once with the screen “live” (no problem), and once with the screen killed by ctrl-caps-eject and it reproduced the crash. It’s hard for me to do this many times in a row, but could it be that something happens over time because the screen is killed? Of course the preferences for "energy saver’ for computer and screen sleep are on “never”.
Hello again. At the risk of monologuing, I want to add that it seems that I have found a trick to escape the bug::. Instead of turning off the screen (and keyboard) with ctrl-caps-eject, I turn them off with the F1 and F5 function keys. By doing so, it seems that there is no problem. At least I could run several times my software for long periods of time in darkness with no crash, whereas with ctrl-caps-eject i was getting the problems described above.
Does anyone have an idea of what the ctrl-caps-eject routine does besides turning off the screen and keyboard? Isn’t that a strange bug of OS X ?
Could you go to your system preferences for the keyboard and look up what ctrl-caps-eject is set to? I don’t have that combination set on my machine.
Thank you for your reply. It is not listed in the System preferences keyboard shortcuts, but it seems to be a standard Mac OS shortcut :, and is listed on this page for instance::
under the label: Control–Shift–Power button* or Control–Shift–Media Eject ! Put your displays to sleep.
Thank you for the offer to help. I’m not sure that I understand what you would need exactly besides the crash reports that I have already sent. Please let me know and I will try to provide it.
A project which crashes like this when we press that key combination and a bug report in our feedback system. Posting here is not the same as filing a bug report.