BUG: Force Quitting when Logos hangs does not quit the program

Devs,

Logos has been hanging on me quite a bit, and I noticed that force quitting does not completely kill the program. It kills it enough to open a new instance of the program, but the other instances remain hung in the background. Here are screen shots:

Force quitting the gdb-apple-darwin i386 process kills the hung Logos 4 instances. Didn't think to grab logs. When it happens again, I come back and attach them.

Keep up the good work guys!

Find more posts tagged with

Comments

Keep Smiling 4 Jesus :)

Observation: with 2 GB RAM installed and 1.6 GB of Page Outs, seeing potential for RAM upgrade.

Suggest rebooting Mac - reset Page Outs to 0 bytes.

Keep Smiling [:)]

Michael Kares

https://community.logos.com/discussion/comment/194181#Comment_194181

I may do that.

Michael Kares

https://community.logos.com/discussion/comment/194588#Comment_194588

And here I thought Mac's never needed to restart.... ;-) Thanks KSFJ

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/194589#Comment_194589

And here I thought Mac's never needed to restart.... ;-) Thanks KSFJ

Memory leaks afflict Mac's as well as PC's - have learned to use Apple's Activity Monitor to watch memory usage along with how responsive programs feel (have noticed a correlation between Page Outs and slow - provided justification for memory upgrade when running many programs).

Keep Smiling [:)]