[BUG] On Chrome launch, using up a lot of CPU (100% on one core) and crashes after a while (Ubuntu) about thegreatsuspender HOT 20 CLOSED

Have you tried disabling the extension and then restarting? If you have any currently suspended tabs, then I would recommend clicking the 'enable all' button first and once all your tabs have reloaded (ie. not suspended anymore) then try to disable the extension and restart chrome and see if you have the same problem. Ideally, it would be good to be able to isolate my extension from your issue.
If this does not fix your problem and it really does seem to be my extension consuming your CPU then I can take a look at optimising the code that gets performed on startup - looks like I'll be doing another release pretty soon anyway.

from thegreatsuspender.

I can confirm that by de-activating the extension, my Chrome does not block
on startup : the CPU usage is somehow "reasonable" : 25% on 2 cores
(considering it has to load a huge number of tabs at once, which is a
stupid behavior for a power-user use case, and is the whole point of this
extension). But it does no crash.

Again, I can also confirm that, when the extension is active, by simply
focusing each suspended tab once on start-up, the CPU usage quickly drops
to ~ 12% on 2 cores, which is a much better CPU usage (alongside the memory
usage gain), and my chrome does not crash. If I don't do that, the CPU
usage stays very high until the chrome thread is blocked and I have to
reboot it manually. (kill -9 -1 comming in handy).

2013/2/17 deanoemcke [email protected]

Have you tried disabling the extension and then restarting? If you have
any currently suspended tabs, then I would recommend clicking the 'enable
all' button first and once all your tabs have reloaded (ie. not suspended
anymore) then try to disable the extension and restart chrome and see if
you have the same problem. Ideally, it would be good to be able to isolate
my extension from your issue.
If this does not fix your problem and it really does seem to be my
extension consuming your CPU then I can take a look at optimising the code
that gets performed on startup - looks like I'll be doing another release
pretty soon anyway.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-13690983.

from thegreatsuspender.

just to be clear, when you are restarting your chrome, are all your tabs suspended? or are they in a normal 'unsuspended' state? assuming they are all suspended - do you have the same issue if you click 'unsuspend all', waiting for all your tabs to reload, shut down chrome and THEN try to restart?
just trying to find out if it is the suspended tabs causing the issue or something else with the plugin that happens on chrome startup.

from thegreatsuspender.

Hi, sorry I took so long to respond but I didn't have access to my ubuntu
laptop to test this.

So yeah, I confirm that I have this behavior on restart with most of my
tabs suspended (expect of course the white list matching tabs).

I can also confirm that when tabs are suspended on start-up, the
chrome--no-startup-window process is eating up 100% of CPU on all 4 cores,
until Chrome gets suspended by the OS. This process seems to be the main
Chrome process : if I kill it, it kills all Chrome windows + other chrome
processes.

When tabs are NOT suspended (Reload all + close + start again as you said),
the behavior is the same as when the extension is de-activated : all four
CPUs are used at maximum capacity until all tabs are loaded (which is the
usual behavior before I installed the extension) then CPU usage goes down
to ~ 20% on one core (still with the chrome--no-startup-window process
eating this resource).

Si I guess it's the suspended tabs that trickles the issue : does this help
your investigation ?

2013/2/18 deanoemcke [email protected]

just to be clear, when you are restarting your chrome, are all your tabs
suspended? or are they in a normal 'unsuspended' state? assuming they are
all suspended - do you have the same issue if you click 'unsuspend all',
waiting for all your tabs to reload, shut down chrome and THEN try to
restart?
just trying to find out if it is the suspended tabs causing the issue or
something else with the plugin that happens on chrome startup.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-13714375.

from thegreatsuspender.

[Update] after the chrome launch without suspended tabs, when the extension
activated suspended tabs after the given period of time (5 minutes for me),
it started to eat up a lot of CPU just as when re-starting the browser.
Going over all tabs helped again reduce the CPU usage back to normal.
So it seems the simple fact of suspending at once a lot of tabs is enough
to activate this problem. Hope this helps !

2013/2/18 Mathis Gardon [email protected]

Hi, sorry I took so long to respond but I didn't have access to my ubuntu
laptop to test this.

So yeah, I confirm that I have this behavior on restart with most of my
tabs suspended (expect of course the white list matching tabs).

I can also confirm that when tabs are suspended on start-up, the
chrome--no-startup-window process is eating up 100% of CPU on all 4 cores,
until Chrome gets suspended by the OS. This process seems to be the main
Chrome process : if I kill it, it kills all Chrome windows + other chrome
processes.

When tabs are NOT suspended (Reload all + close + start again as you
said), the behavior is the same as when the extension is de-activated : all
four CPUs are used at maximum capacity until all tabs are loaded (which is
the usual behavior before I installed the extension) then CPU usage goes
down to ~ 20% on one core (still with the chrome--no-startup-window process
eating this resource).

Si I guess it's the suspended tabs that trickles the issue : does this
help your investigation ?

2013/2/18 deanoemcke [email protected]

just to be clear, when you are restarting your chrome, are all your tabs
suspended? or are they in a normal 'unsuspended' state? assuming they are
all suspended - do you have the same issue if you click 'unsuspend all',
waiting for all your tabs to reload, shut down chrome and THEN try to
restart?
just trying to find out if it is the suspended tabs causing the issue or
something else with the plugin that happens on chrome startup.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-13714375.

from thegreatsuspender.

very useful. thanks heaps for that.
and you said it only happens if you have about 50+ tabs being suspended at the same time?
so, if you had, say only 20 tabs (or even 10? 5?) then you don't have any problems?

from thegreatsuspender.

also, it might be useful to know which version of chrome and ubuntu you are using.

from thegreatsuspender.

Well it's a pretty interesting test : I opened my Chrome session linked to
another email (by cliking on the person icon of chrome and switching to
another connected account), which usually didn't have this issue upon
loading on the same machine with very few tabs openned (4) and no withelist
tabs neither pinned tabs.

So I openned several tabs (<20), pinned some of them, added some of them to
my whitelist, and suspended the rest. All this in order to replicate the
situation I'm in with my other chrome account but with much less tabs in
each state.

This resulted in a partial over-use of my CPU on loading this chrome :
around 50% on 2 cores. I waited for a few minutes without change, and
again, going over all the tabs manually made the CPU usage fell down to the
low level it was supposed to be. So the issue is definitely replicable, but
seems to be linked to the number of tabs open.

I guess that enables us to coin this down to a performance issue, but I'm
not sure what would cause it, I haven't had time to look deeper into your
code and I suppose it might be related to the Chrome way of handling things
in their own codebase ?

About my conf : Ubuntu 11.04 (pretty deprecated, haven't had time to update
but planning on going to MintLinux in the future) + Chrome latest stable
for linux (Version 24.0.1312.70).

2013/2/18 deanoemcke [email protected]

also, it might be useful to know which version of chrome and ubuntu you
are using.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-13739172.

from thegreatsuspender.

Do you have image preview on?
If so, does it still happen if you turn it off? (go to options, turn it off and make sure you click save).
I have found on mine, that if I have image preview on, and suspend all the tabs at once, chrome will use up one CPU (25%) for quite a while even after all tabs have finished suspending.
Does this sound like the same issue?

from thegreatsuspender.

sorry, by preview i mean screen capture.

from thegreatsuspender.

Yup I thought of that at first but no I never turned it on. Sorry I should
have mentioned that earlier on.
Le 19 févr. 2013 09:23, "deanoemcke" [email protected] a écrit :

sorry, by preview i mean screen capture.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-13761601.

from thegreatsuspender.

Of course I want to clarify that this issue is specific to the linux
version of Chrome : this does not happen for approximately the same initial
conf (number of tabs, pinned tabs, suspended tabs etc) on a Windows 7
computer and last Chrome stable.

I guess the next step if the issue is still not reproducable, is to try to
upgrade my Ubuntu and see if the pb persits ?

2013/2/19 Mathis Gardon [email protected]

Yup I thought of that at first but no I never turned it on. Sorry I should
have mentioned that earlier on.
Le 19 févr. 2013 09:23, "deanoemcke" [email protected] a écrit :

sorry, by preview i mean screen capture.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-13761601.

from thegreatsuspender.

True. Thanks for clarifying this. I have been doing all my testing on a Win7 machine and it seems fine suspending 60+ tabs.
Will have a little play around tomorrow to see if it's any different on my work machine (i think running 11.10 ocelot). If I can't detect any issues I think I'll go ahead with the new release.
Thanks again for taking the time to answer all my questions :)

from thegreatsuspender.

No pb, I kinda hope it's not reproduceable on any other linux distrib so
that we know it's a very specific bug that won't impact anyone else (even
though it means I have to live with it for now).

Anyway, thanks again for your work, I badly needed it and since I'm a
developer myself, I figured the least I could do is help you iron out some
bugs I noticed ! If I can manage to spare anytime in the future, I might
even get to look at your code further to see how you managed this, I'm
pretty interested :)

Good luck with the new release and thanks for delivering this to the web
store. Rest assured that some of us are very grateful for your work !

2013/2/19 deanoemcke [email protected]

True. Thanks for clarifying this. I have been doing all my testing on a
Win7 machine and it seems fine suspending 60+ tabs.
Will have a little play around tomorrow to see if it's any different on my
work machine (i think running 11.10 ocelot). If I can't detect any issues I
think I'll go ahead with the new release.
Thanks again for taking the time to answer all my questions :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-13762981.

from thegreatsuspender.

Tried to replicate issue on a newer version of Ubuntu without success.
Keen to hear if you upgrade fixes the issue.

from thegreatsuspender.

Indeed a friend of mine also confirmed he couldn't reproduce this bug on
his ArchLinux distro. So I suppose this is linked to a pb with my Ubuntu
distro (which is quite intruiging BTW, if I had time I would be interested
in figuring out what the hell is happening :)

I'll keep you up to date on this bug when I upgrade my linux distro.
Meanwhile I'm really gratefull you took the time to investigate this with
me.
Best of luck with the extension, hope you manage to make a few bucks out of
it ! (at least by putting it on your resume for a job application, it's a
strong credential).

2013/2/21 deanoemcke [email protected]

Tried to replicate issue on a newer version of Ubuntu without success.
Keen to hear if you upgrade fixes the issue.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-13883031.

from thegreatsuspender.

I thought this was only in my notebook. I'm having the same issue with Chrome especially starting chrome would use up almost 100% cpu but then the cpu goes down after awhile. If i open tabs that have to many pictures even small lined up pictures would make the scroll bar sluggish or lag sometimes not working. But if i use the arrow keyboard it would scroll but slow. By the way, I'm one Linux Mint KDE. Then again, I also use Firefox but the cpu only went around 70% at start and opening the same page (that have small lined up pictures) the scroll bar works smoothly no lag.

from thegreatsuspender.

here is the image on first starting Chrome. Well, I using Asus X401U with AMD-C60 1GHz and 2GB ram only. So it might be because of my notebook specs.

from thegreatsuspender.

Hello,

I have no crash on my chromium, but adding this extension clearly adds up a lot more CPU usage
I can reproduce it by manually suspending a tab - 20 or 1 gives the same CPU usage.
I'm on Fedora 17 with chromium 23.0.1271.95

Thanks

from thegreatsuspender.

Closing as it is an old issue and extension has been significantly changed since then.

from thegreatsuspender.