Re:Something is deeply broken in OS X memory management
by obituary_latte on Monday April 23, 2012 @12:59PM
(#3879787)
Ah yes. The dreaded Chrome renderer never enderer.
I too have experienced the Chrome issue enough that I don't even try to close it normally anymore. Force quit is the only way I exit Chrome. Thankfully, the restore tabs functionality works well.
Re:Something is deeply broken in OS X memory management
by ricardobeat on Monday April 23, 2012 @06:23PM
(#3881282)
I'm glad to see I'm not the only one. This drives me crazy every time.
Re:Something is deeply broken in OS X memory management
by kirbysayshi on Monday April 23, 2012 @01:20PM
(#3879890)
Firefox 12 does this too, on both my MB Pro and iMac. I think it has to flush so many caches that disk I/O just takes forever. This is purely conjecture, though.
Re:Something is deeply broken in OS X memory management
by ticks on Monday April 23, 2012 @01:56PM
(#3880074)
Not sure if it will help, but have you tried running Firefox's hidden profile manager and created a new profile? Firefox was horrible to run on OS X for me, it would drag the whole system down, but since changing to a new profile it has run like a dream and not reverted back.
Re:Something is deeply broken in OS X memory management
by blacksmith_tb on Monday April 23, 2012 @07:37PM
(#3881605)
Creating a new FF profile made a significant difference for me, too, when I did it recently (for the first time in a couple years). I suspect that will be true on any OS, if you do a fair amount of installing and removing extensions, user scripts, etc.
Though I did improve matters drastically by telling mds not to index my (Linux) MP3 server and my Time Machine drive. That made it go from nearly unusable to just frequently annoying.
The other crazy thing I've been seeing is it routinely takes Chrome minutes to shutdown -- in fact, pretty much every time I try to reboot my MBP without shutting down Chrome first, the shutdown process times out trying to exit Chrome.