Log in

No account? Create an account
Previous Entry Share Next Entry
Anyone know why Chrome (maybe Javascript) sometimes goes haywire when it sits in the background?
I'm one of those people who tends to have open tabs in my browser. Like, *lots* of open tabs. Like, 50 or more.

I'm not sure if it's a recent change, but the past week I've been noticing a tendency for Chrome to start chewing 50% of my CPU (that is, two cores) when I'm not doing anything. When I investigate, it always seems to be that two tabs that are *not* currently on top are each eating 25% of CPU. It's not the same tabs each time, but it does always seem to be "heavy" pages that are likely to be full of Javascript. The problem usually goes away simply by finding and clicking on that tab, bringing it to the front. My best guess is that the Javascript on these pages is getting into some kind of frantic loop, doing something that isn't allowed while it's in the background, but that's just a guess.

Anybody have any concrete ideas what is happening here? I ask mostly out of idle curiosity, but also because there may be an anti-pattern that I want Querki to avoid...

  • 1
Windows 7, relatively up to date.

Fascinating. I have Chrome on Windows 7 with 3 different user profiles active most of the time (though I admit, I usually cap out at 15 tabs per profile) and have noticed no issues. On Ubuntu, however, it blows up daily.

I have no idea why, but it does it to me too, but with flash-- I go and end whatever process is chewing up memory or CPU (it varies which one it starts chewing) and I get "Shockwave flash has crashed" as a result. It's been doing that for months if not years, on an irregular basis.

Well, Flash is qualitatively different, enough so to count as a different problem. It's basically a whole separate product that is hosted inside the browser window. And it's famously a little bit unreliable...

I believe I've seen similar behavior under OSX (older versions 10.5 and 10.6), also associated with Flash. I tend to run a flash-blocker now, which seems to help, but I haven't done any serious testing. I run LOTS of tabs in multiple windows.

The same thing happens to me. I haven't figured it out either (except when it's Facebook, the most obvious culprit).

I also have it happen that when I end what looks like the most rogue process in Task Manager, it either crashes Flash or crashes Chrome entirely.

I feel like Flash might be the culprit rather than Javascript but I don't have a lot of solid evidence for that guess. Sometimes there'll be a tab with a video clip in it somewhere and if I load the tab while looking at it, nothing happens, but if I load it in the background, the video starts playing itself unbidden. Not only annoying but it gives me a variety of concerns.

I use chromium,and on a different OS, so I haven't seen the same issue, but related ones. Chrome does have it's own built in process monitor that you can launch to get more insight into exactly what is going on...

Edited at 2014-04-12 07:23 pm (UTC)

Oh, sure -- that's how I'm addressing the problem. I go into Chrome's Task Manager, which tells me which processes are causing the problem, then front the tabs from those processes. Almost always causes the problem to go away...

(Deleted comment)
does not happen to me under win7 on several machined but what i DO get is thta it eats like 90% of my MEMORY (rather then cpu) regularly. nom. i tend to have anywhere form 30 to 50 tabs open

Not really surprising: Chrome can eat a *huge* amount of RAM, since it has roughly a process per tab. Only reason that doesn't cause me problems is that this is my development machine, and has a ton of memory (12G), so the fact that Chrome is taking a Gig or two is okay...

  • 1