Behind the power curve...

[alexpgp]

After closing down Chrome (i.e., it no longer shows up as an application in Task Manager), there would appear to be a dozen Chrome processes still running, and while they may not be sucking down all that many CPU cycles, they are most certainly occupying about a third of a gig of memory.

I shall endeavour to stay calm and muddle through...

Comments

[n5iln.livejournal.com]

Chrome does appear to have a problem with graceful closure of processes, as well as with creation of memory leaks. It has since its first release on the WinXX platform.

Just my casual observation...

[bandicoot.livejournal.com]

Adobe Reader does that, too. It's one reason I switched to Foxit Reader. I got tired of going into Task Manager to shut down all the Adobe processes.