Logos Crash - often unable to -kill

Howdy,

It seems as though roughly 60% of the time Logos crashes on my Mac, I'm unable to Force Quit the application. I'm also unable to "sudo kill -9 <pid>", which means I have to restart my entire computer in order to get back in to the application.

Did a little more digging, and this is really confusing: I can kill -9 the ppid, but it doesn't help because the ppid of that process is the Logos process.

Something is very weird here, and with Logos crashing every other day, it's a HUGE pain to have to restart the entire machine and close everything else I'm working on. Please at least make it possible to recover from a crash.

Find more posts tagged with

Comments

TCBlack

Logs would be helpful.

in the Mac Diagnostic logging is already enabled, Mac Troubleshooting page has How to Report Bugs in Logos 4 Mac

Joey Mavity

https://community.logos.com/discussion/comment/223853#Comment_223853

As that page says, "after Logos 4 Mac crashes (and before reopening it)." As per my description, it never completes crashing.

I just recreated the crash that hung the process without being able to terminate it. This time it terminated cleanly through the crash. To repeat the crash:

Open Logos
Go to a Bible passage (ex: "go to matthew 1" - I used ESV, not sure if it matters)
Right-click tab, select "Open in a floating window"
Click on the "+" for a new tab
In the resources, select ESV (from either the 'icon' view or the 'list' view on the right)
Crash

4073.Logging.zip

The first time I did this, the process hung and it was impossible to kill -9 the pid for logos and impossible to kill the ppid. The parent process' ppid was Logos, making the whole thing circular. The second time I did this, it crashed cleanly and I attached the log file. The third time I did this: no crash.

Mike S.

I remember when I've run into this problem it is because the gdb (gnu's debugger) is attached to the logos process... just do a soft kill of the gdb process and your logos process will disappear.

To verify that this is the case, check to see if a gdb process exists ("ps auxww | grep -i gdb | grep -v grep" or do a search in the activity monitor), and if it does, check the ppid for the logos process ("ps -afx | head -1; ps -afx | grep -i logos" or... again, check the activity monitor's process details for the undying logos process)... if its there and the ppid for Logos is the same as the pid for gdb, kill gdb ("kill <pid of gdb>")

Joey Mavity

https://community.logos.com/discussion/comment/223870#Comment_223870

Thanks for a helpful response, Mike. I'll try a soft kill with the debugger, I think I went straight to -9.