Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 89585 System hang upon opening a new tab
Starred by 5 users Reported by, Jul 18 2011 Back to list
Status: IceBox
Owner: ----
Closed: Aug 2012
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

  • Only users with Commit permission may comment.

Sign in to add a comment
On some random occasions, Chrome and my system hangs when I open a new tab (regardless of how, such as simple new tab or open link in new tab).

All I can tell about it is that the Window with the tab becomes completely unoperable, the process responsible for that tab/window each one of my CPU cores completely, and my computer becomes overall extremely unresponsive.

This continues for ever as far as I can tell, though I haven't really tested that. The longest I've let it churn about is about half an hour, so I don't think it was about to solve it on its own. The problem disappears as soon as I kill the Chrome process that does this.

In task manager, the I/O counters remain unchanged, number of threads remains unchanged, handles remains unchanged, and on my last attempt I enabled display of other statistics and saw that the hanging process used 10000 GDI objects. That's not normal I think. So I presume it was extremely aggressively trying to create new ones even when it had hit some sort of hard limit for them and thus hanging itself and OS?

Anyway, I lose the tabs in that window each time, they don't appear in recently opened pages or anything because of the need to kill the process.

This happens on Windows 7, and after looking around, Vista would suffer from it too at the same point ( ).

Another point, most apps, even Chrome, normally uses at most 4000-5000 GDI objects and even that is somewhat rare.
"the process responsible for that tab/window each one of my CPU cores completely"
... eats, not each
Comment 2 by Deleted ...@, Aug 1 2011
I'm having a similar problem. Sometimes when I open a new tab and type in the address bar whether it be or searching, such as typing in the address bar "puppies"... the page hangs. It's unresponsive. I think this may be related...
I'm getting the same issue. "chromedeck" often seems to cause it. I have ati/intel switchable graphics on a Lenovo W500 running W7 x64. I can guess it could be a gpu driver issue, but the effect is massive. System takes many minutes to even get a task list. CTRL-ALT-DEL can fail to respond. Only once I tried to debug properly, and that took hours. Something running very high priority in the kernel.

This seems to happen a lot more rapidly on occasion since the last update to Chrome, upon opening some pages (Wikipedia's front page surprisingly frequently though it's not the only one) the GDI object count skyrockets from less than 200 up to 10,000 (I had task manager open during one of these to see it). Killing the process solves this quickly but repeats almost immediately if I don't close the whole session and start again.
The summary of this issue should be "system hang from GDI object starvation" or something instead of the current new tab one.
Comment 6 by, Nov 2 2011
Hi miika, could you tell me WIkipedia URI you saw lots of GDI objects usage?
I tried on 
* English
* Japanese
But, number of GDI objects is 49(render process), 341(browser process).

If you have a chance, please try to use GDIView or another tool to show details of GDI object count.

Thanks in advance.
Comment 7 by, Nov 11 2011
This happens frequently to me too. I've learned to recognize the symptoms and start Task Manager fast enough to be able to kill the offending Chrome process before it gets too bad. (Not that I really enjoy having had to learn that, mind.) The GDI object count ends up being 10,000 (I guess that's some hard-coded maximum per process in Windows.)

However just now this bug pretty much took down the whole OS, with no other program able to do its thing, nor did W7's CTRL+ALT+DEL screen work.

As a workaround until this can be fixed for good, would it be possible to add a watchdog sort of system that would kill Chrome processes that use over >6000 GDI objects?

Chrome 17.0.932.0
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Graphics card: Geforce GTX 460, driver version 280.26
Comment 8 by, Nov 11 2011
I ended up writing a quick hack of a watchdog in C# myself.
Not sure if it works... hoping I don't have a chance to find out :-).

Source and binary available on Bitbucket,
Haven't had the problem for at least two days now. I'm using bet beta releases btw and currently using 16.0.912.21 beta-m (which apparently is outdated again). The highest GDI count has been ~1500 for a while and currently it seems to be mostly fonts with ~20 DCs and bitmaps each (according to gdiview). And I meant the as the one causing the GDI spike, before I even selected which language of their site I'd use.

I'll see if I can somehow coax something to happen for this, though currently it seems the problem has gone into hiding.
Project Member Comment 10 by, Aug 10 2012
Status: IceBox
Closing old bug as obsolete. Please file a new bug (with details) if this problem is still occurring for you.
Comment 11 by Deleted ...@, Aug 21 2012
Same problem.  But if you open a new tab next to the frozen tab, the frozen tab unfreezes.  Try it.  Not a perfect solution but it works.
Project Member Comment 12 by, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 13 by, Mar 11 2013
Labels: -Area-Undefined
Sign in to add a comment