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

Page 1 of 1 (5 items)
This post has 4 Replies | 0 Followers

Posts 505
Michael Kares | Forum Activity | Posted: Fri, Nov 19 2010 9:50 AM | Locked

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!

Posts 15805
Forum MVP
Keep Smiling 4 Jesus :) | Forum Activity | Replied: Sat, Nov 20 2010 7:00 AM | Locked

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 Smile

Posts 505
Michael Kares | Forum Activity | Replied: Mon, Nov 22 2010 10:16 AM | Locked

I may do that. 

Posts 505
Michael Kares | Forum Activity | Replied: Mon, Nov 22 2010 10:17 AM | Locked

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

Posts 15805
Forum MVP
Keep Smiling 4 Jesus :) | Forum Activity | Replied: Wed, Nov 24 2010 10:26 PM | Locked

Michael Kares:

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 Smile

Page 1 of 1 (5 items) | RSS