Customer running app on OS X is reporting a crash log on launching app. Build is Carbon, I do not build apps for Windows so this is Mac-only. I’ve gone over the report but can’t figure out what’s causing it. They were using the app just fine last week. They claim nothing has changed regarding software installed or updates. They’ve also tried rebooting the computer.
Can anyone provide some assistance in decoding this crash log? Thank you very much to anyone who can provide assistance!
Date/Time: 2016-10-03 16:03:19.905 -0400
OS Version: Mac OS X 10.11.6 (15G1004)
Report Version: 11
Anonymous UUID: 6F672F6E-3B5D-0060-C9E4-C97F2E3F6F25
Thank you for the replies. I’ve already almost completed the migration to Cocoa. This is an older version of the app that is legacy for users who haven’t paid for an upgrade.
I’m running this legacy version on Sierra with zero issues and have been testing everything through the betas on multiple computers. This doesn’t mean it’s perfect but I haven’t ran into any issues, and have only had one crash report out of a fairly large user base.
So yes I already know to switch to Cocoa. Pertaining to my original question - is there anything else of relevance in the crash report? Or is it too generic?
[quote=289708:@C Mana]Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.company.appname 0x02972f03 App.Event_Open%%o + 27526[/quote]
Doesn’t this mean something in App.Open is causing the crash?
I’d put System.Debuglogs every other line in there then have the customer run it and send back what’s in the Console. The debuglog that doesn’t make it to Console tells you which line crashes.
This is a good idea, if in fact a single line of code in the app’s open event is causing the crash. I assumed that might be the case, but wondered if someone smarter than I could confirm that.
Thank you both. I will try to debug the line of code. Very strange that this happened randomly for this one person. They’ve used the app for years, and even last Friday was having no issues.
I hope the line of code that ends up being the culprit makes sense. If it seems like a benign instruction with no obvious cause as to what could be nil or why, that will be a head scratcher.
No default window. The window is opened in the open event of the application.
I will post the line of code if I can find it. Working on the debug lines now. There’s a lot going on in the app’s open event. Then I’ll send the new build to the customer and see what she reports.