You're Not Releasing the Chrome.exe process about thegreatsuspender HOT 7 CLOSED

i'm no expert, but i was curious about this. i'm on centos 6.4 and while there are more 'chrome' processes than listed in the TaskManager, a lot of these are chrome's own (eg the sandbox etc). all the rest were visible in the chrome task manager.

from thegreatsuspender.

Interesting. I'm pretty sure on Windows all the processes are in the TaskManager. But, regardless, it's clearly happening. I suspended tons of tabs and the memory use didn't go down that much. However, sometimes it DOES release the processes.

from thegreatsuspender.

hmm...well afaik the sandbox processes are 'outside' the browser itself, so the TaskManager won't know about them. i suppose you've checked the PIDs of the processes that are hanging around and they were 'formerly' tabs that have been suspended?

from thegreatsuspender.

yes, I confirmed by matching on memory usage before I suspended - it matched exactly. Plus I confirmed no other tabs were attached to that process.

from thegreatsuspender.

For mine, it seems working fine. The Process IDs for only the tabs loaded show up, while suspended tabs do not.

from thegreatsuspender.

@scottedwards2000 Just wondering if you are still encountering this behaviour?
Have you tried to the GitHub version of the extension? It will be updated on the webstore very shortly.

from thegreatsuspender.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.

from thegreatsuspender.