Sorry, I meant to say this also happened on Mac OS X 10.6.5 as well.

Verified label updated by AutoAllocator, contact AmolK or KrisR for details

I think it is likely that the GPU hung and that was what caused the GPU watchdog to terminate the GPU process in an attempt to recover, unsuccessfully in this case. If that is the case then the GPU watchdog is working as intended.

Is there a particular web page that makes this happen?

Adding kbr.

No particular page and it sometimes happens when minimized. I usually have Chrome open so the watchdog message would always be there. I'll keep Chrome closed for a while to see if it happens.

@jcarbaugh: Is there any correlation with pages that use WebGL or do you have "GPU accelerated compositing" enabled in about:flags ? 

No WebGL that I'm aware of and "GPU accelerated compositing" is not enabled. I usually have two Gmail tabs, GitHub, and a few tabs of my own web apps that I'm working on. So no obvious WebGL on any of those.

Went all day yesterday without opening Chrome and no freezes. Using Chrome today and I've had two freezes, both writing the GPU watchdog message in the logs. I'll keep alternating this week. Also updated to latest dev channel release a few minutes ago.

I understand that freezes could be coincidental so I'm trying to get a freeze with Chrome closed so that I can rule it out.

This just happened to me as well. Found this as the last line in the logs which lead me to this issue:

Jan 12 12:32:39 kamino [0x0-0x35035].com.google.Chrome[813]: [846:21263:476614094117614:ERROR:/b/build/slave/chrome-official-mac/build/src/chrome/gpu/gpu_watchdog_thread.cc(220)] The GPU process hung. Restarting after 10000 seconds.

No other Chrome messages or other errors immediately before that line. This is the first time that this has happened to me. The page I was opening at the time was pretty random:

http://www.mozilla.org/support/firefox/adblock

I'm running v10.0.634.0 and GPU compositing is disabled for me as well. Mac Pro, OSX 10.6.6, Quad-Core Intel Xeon 2.8ghz, ATI Radeon HD 2600 XT

Also found the same messages in kernel.log as in the original report above --

Jan 12 12:32:37 kamino kernel[0]: ** Device in slot: SLOT-1 **
Jan 12 12:32:37 kamino kernel[0]: ** GPU Debug Info Start **
Jan 12 12:32:37 kamino kernel[0]: 0x00009588
Jan 12 12:32:37 kamino kernel[0]: 0x000000d6

... etc until I rebooted

I've been experiencing this as well. Same exact problem. Had to roll back to a stable Chrome and giving that a go..

OSX 10.6.6 / iMac 2.4 Core2Duo

11-01-18 11:59:16 AM	[0x0-0x23023].com.google.Chrome[263]	[287:24587:181634895933:ERROR:gpu_watchdog_thread.cc(220)] The GPU process hung. Restarting after 10000 seconds.

apatrick, could this be related to graphics card info collection?  also, why would we try to restart the process after 10,000 seconds?

I think it might well be the GPU info collection. We could blacklist the HD 2600 on Mac if it is specifically that card that has issues but we might have to identify the device in a way that does not exercise whatever code is hanging. Adding zmo.

The error message is wrong. It is 10,000 ms or 10 seconds for the watchdog timeout. I'll fix that.

Can you open chrome and type in about:gpu in the address box?  and let me know if it hangs.

Loaded without hanging for me.

Ok, so gpu info collection does not trigger this hang, at least not directly.  I am curious on why gpu is required.  Seems like you are not using webgl, you haven't enabled accelerated compositing.  Did I miss something that could use gpu?

jcarbaugh, can you copy the content on about:gpu here?  We might want to blacklist your gpu.

Chrome Version
Data exported	Tue Jan 18 2011 17:48:32 GMT-0500 (EST)
Chrome version	10.0.634.0 (Official Build 70875) dev
Driver Information
Initialization time	1514
Vendor Id	0x1002
Device Id	0x9583
Driver version	1.6.26
Pixel shader version	1.20
Vertex shader version	1.20
GL version	2.1
Diagnostics
None

A long shot but Apple issued a firmware update to resolve stability issues with the HD 2600 XT. It was in 2008 and it might have been bundled with a regular system update since but is there any possibility you don't have it installed?

http://support.apple.com/downloads/ATI_Radeon_HD_2600_XT_Firmware_Update

It's interesting that there was also a firmware update for the 1900, another ATI card we blacklisted on stability issues.

re: firmware update - I downloaded it but it cannot be applied. According to the following:

http://support.apple.com/kb/TS1237

"This update will automatically be offered to affected computers via Software Update."

"Your computer does not need this update."

The message received while attempting to install the 2600 XT firmware update.

I just found out that a coworker is also having this exact same Chrome+iMac freezing issue.

@thakis: I think assigning this bug to me happened by a mistake. I never dealt with GPU-related code.

I am also experiencing this issue - and with increasing frequency.

mnaganov: Yes, sorry.

I am also seeing the same problem. 

The error in the system log is, 

Feb  6 13:54:35 xxxxxx-xxxxx-iMac [0x0-0x2d02d].com.google.Chrome[3249]: [5095:17675:56404871957573:ERROR:/b/build/slave/chrome-official-mac/build/src/chrome/gpu/gpu_watchdog_thread.cc(220)] The GPU process hung. Restarting after 10000 seconds.

I only seem to receive this problem when using WebGL. In all other situations, Chrome performs flawlessly for me. The quickest way that I have found to replicate the issue on my computer is to go to http://doesmybrowsersupportwebgl.com 

I have attached a file containing my hardware profile and the Chrome version that I am using.

profile.txt 979 bytes View Download

I've also had this issue, although I do not think I am loading webgl. My iMac crashes when loading www.jaygeorge.co.uk/the-granary-barn repeatedly. I think it may be because the site is using Modernizr to run a WebGL test.

I have interestingly tried all 3 versions of Chrome: Stable, Beta, Dev and get crashes on all three. Very frustrating.

Also I can confirm http://doesmybrowsersupportwebgl.com freezes my computer.

Also I can confirm http://doesmybrowsersupportwebgl.com freezes my computer.

Can you at least tell us how to disable WebGL until this issue is fixed? fed up of my Mac crashing.

Can you at least tell us how to disable WebGL until this issue is fixed? fed up of my Mac crashing.

Hi jaygeo, sorry to hear this is still happening.  zmo, let's blacklist this card and I'll try to get one for us to test on.  

in the mean time, anyone experiencing this can diable webgl by running chrome with --disable-webgl from the terminal, i.e.

open -a /Applications/Google\ Chrome/ --args --disable-webgl

for anyone else having this problem and wants to disable WebGL you need to close Chrome, then open terminal and paste this... open /Applications/Google\ Chrome.app/ --args --disable-webgl

I had to add the .app on the end of hbridge's suggestion (thanks for replying fast hbridge).

You have to do this every time to open Chrome, rather than double clicking your dock icon or whatever.

I can confirm that going to http://www.doesmybrowsersupportwebgl.com/ no longer freezes my computer, instead I get a "Nay" to say WebGL isn't running on my computer :).

If I don't reply again it means I haven't had any issues with Chrome since I disabled WebGL and therefore WebGL it is definitely the cause of freezing.

zmo, can we blacklist the OS/card combination described in Comment 31 (which seems to be the same one from the original report) while we wait to debug this on similar hardware?

yes, please note that the card we want to blacklist is a radeon hd 2600 pro,
not the 2600 XT

@40 - It happened to me on a Radeon HD 2600 XT as well. 

+1 for 2600 Pro


ATI Radeon HD 2600 Pro:

  Chipset Model:	ATI,RadeonHD2600
  Type:	GPU
  Bus:	PCIe
  PCIe Lane Width:	x16
  VRAM (Total):	256 MB
  Vendor:	ATI (0x1002)
  Device ID:	0x9583
  Revision ID:	0x0000
  ROM Revision:	113-B2250F-219
  EFI Driver Version:	01.00.219
  Displays:
iMac:
  Resolution:	1920 x 1200
  Pixel Depth:	32-Bit Color (ARGB8888)
  Main Display:	Yes
  Mirror:	Off
  Online:	Yes
  Built-In:	Yes
Display Connector:
  Status:	No Display Connected

I also have the HD 2600 (same as the previous commentor).

Not sure if this is the same issue but Moderniz 1.6 does not work well with Chrome 9.0.597.94 on Windows.  This is also tracked at the Moderniz Github site:

https://github.com/Modernizr/Modernizr/issues/issue/190/

You can see the behavior by viewing any of the "sites using modernizr" referenced on modernizr.com, e.g.:

http://fmbip.com/

I suspect this is because Modernizr works by testing different technologies to determine browser capabilities. I was having a problem because Modernizr was testing for WebGL - hence my computer kept freezing even when I visited sites that apparently did not use WebGL technology (but were optimised using Modernizr).

The Modernizr/webgl issue was solved over in Issue 65369.

To repro, you need to get the experimental-webgl context on a machine with less-than-great GPU hardware,  it seems.

The fix is resolved for Chrome 10.

Paul,

My machine only started freezing when I started working on web design again, and I use Modernizr on all my sites. Additionally when going to http://www.doesmybrowsersupportwebgl.com/ I get a freeze. I'm using an iMac 24 Intel from about 2008 with 4GB RAM and I don't consider it old.

Maybe you're right and it's resolved, but putting the two conditions above together seems more than a coincidence

P.S. I love Modernizr and CSS3Please!

Per discussion with hbridge, we are going to blacklist this card on Mac.

What does blacklist mean? Does this mean I can use Chrome without launching through Terminal now? If so, when? Thanks

Should land it today.  Yes, after it lands, if you use ToT chrome build, then you don't have to launch through commandline flags.

Hi jaygeorge, it means that Chrome will not try to use any GPU-accelerated
features (like WebGL) on machines that have your graphics card.  So yes, it
means you'll be able to launch Chrome without the Terminal.  I don't have an
ETA yet unfortunately.

OK thanks, can you post on here please once Chrome has been updated with my graphics card blacklisted, so that I can try it?

Thanks zmo, jaygeorge, that means if you're on Dev channel,  you'll most
likely get the update Tue/Wed next week.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=74306

------------------------------------------------------------------------
r74306 | zmo@google.com | Wed Feb 09 10:28:53 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/resources/gpu_blacklist.json?r1=74306&r2=74305&pathrev=74306

Blacklist ATI RadeonHD2600 on Mac.

BUG= 68859 
TEST=none
TBR=vangelis

Review URL: http://codereview.chromium.org/6461027
------------------------------------------------------------------------

I'm seeing this behavior on my iMac7,1. It's the 20" model, with a different video card: ATI Radeon HD 2400 XT. Profile with Hardware Overview, graphics card details and Chrome info attached. I can confirm that it also hangs on http://www.doesmybrowsersupportwebgl.com/ and is triggered by Modernizr 1.6.

OS 10.6.6

I do have an external display on this box and will test later if unplugging the ViewSonic VG1930 makes a difference.

system profile.txt 1.1 KB View Download

log messages.txt 193 KB View Download

OK, I'll blacklist this one also.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=74333

------------------------------------------------------------------------
r74333 | zmo@google.com | Wed Feb 09 13:31:00 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/resources/gpu_blacklist.json?r1=74333&r2=74332&pathrev=74333

Blacklist ATI Radeon HD2400.

BUG= 68859 
TEST=none
TBR=vangelis

Review URL: http://codereview.chromium.org/6482003
------------------------------------------------------------------------

I've got the very same issue. I'm on a MacBook Pro 15" 2010 with OSX 10.6.6 and an NVIDIA GeForce GT 330M with 512MB.

I'm using the offical build of Chrome 9.0.597.94

GPU Information
Initialization time   1568
Vendor ID             0x8086
Device ID             0x0046
Driver Version        1.6.26
Pixel Shader Version  1.20
Vertex Shader Version 1.20
GL Version            2.1

@ste.. : Which issue specifically?  A random freeze of the entire system? Is that after visiting a page with WebGL? 

I'll be out for a week, and I don't have easy access to a Mac, reassigning.

@ste..: the 8086/0046 vendor/device ID corresponds to the "Intel Arrandale Integrated Graphics Controller" integrated into some Intel mobile CPUs. Does your MacBook Pro have one of those in addition to the nVidia adapter?

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=74498

------------------------------------------------------------------------
r74498 | zmo@google.com | Thu Feb 10 14:12:35 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/branches/648/src/chrome/browser/resources/gpu_blacklist.json?r1=74498&r2=74497&pathrev=74498

Merge 74306 - Blacklist ATI RadeonHD2600 on Mac.

BUG= 68859 
TEST=none
TBR=vangelis

Review URL: http://codereview.chromium.org/6461027

TBR=zmo@google.com
Review URL: http://codereview.chromium.org/6489010
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=74499

------------------------------------------------------------------------
r74499 | zmo@google.com | Thu Feb 10 14:13:49 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/branches/648/src/chrome/browser/resources/gpu_blacklist.json?r1=74499&r2=74498&pathrev=74499

Merge 74333 - Blacklist ATI Radeon HD2400.

BUG= 68859 
TEST=none
TBR=vangelis

Review URL: http://codereview.chromium.org/6482003

TBR=zmo@google.com
Review URL: http://codereview.chromium.org/6486015
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=74505

------------------------------------------------------------------------
r74505 | zmo@google.com | Thu Feb 10 14:26:23 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/branches/597/src/chrome/browser/resources/gpu_blacklist.json?r1=74505&r2=74504&pathrev=74505

Merge 74306 - Blacklist ATI RadeonHD2600 on Mac.

BUG= 68859 
TEST=none
TBR=vangelis

Review URL: http://codereview.chromium.org/6461027

TBR=zmo@google.com
Review URL: http://codereview.chromium.org/6490010
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=74508

------------------------------------------------------------------------
r74508 | zmo@google.com | Thu Feb 10 14:27:20 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/branches/597/src/chrome/browser/resources/gpu_blacklist.json?r1=74508&r2=74507&pathrev=74508

Merge 74333 - Blacklist ATI Radeon HD2400.

BUG= 68859 
TEST=none
TBR=vangelis

Review URL: http://codereview.chromium.org/6482003

TBR=zmo@google.com
Review URL: http://codereview.chromium.org/6484013
------------------------------------------------------------------------

@vange...: I've got the same issues as jcarbaugh describes in the first post. After using Chrome for a while it freezes my whole machine and only a hard-reset works. I also get that watchdog message in the log. I could reproduce it on sites like http://www.jaygeorge.co.uk/the-granary-barn and http://www.tsn.ca/ but not on http://www.doesmybrowsersupportwebgl.com/

@apatr...: Yes, my MacBook Pro (mid 2010) has two GPUs. One is the integrated Intel graphics chip (for more battery lifetime), the other is the NVIDIA GeForce GT 330M. The MacBook switches between the GPUs dynamically if needed by an application. Chrome always makes use of the NVIDIA chip, due support for WebGL and other stuff I think.

@all: After investigating 3 to 4 hours more - and after writing my entry here - I found out that I'm able to reproduce the freeze without running Chrome. Nevertheless the websites provided here helped me a lot to reproduce the problem more precise. The solution here is that the NVIDIA GPU causes the freeze and after showing my MacBook at the local AppleStore it's now clear that I get a new motherboard because it must have some defect.

I'm sorry for the false alarm here, but that ticket helped me a lot for finding the real problem.

Ahhh, those dynamic switching...

Henry, could we get one of those for testing purpose?  Apparently our gpu information collection fail to locate the nvidia card.

Can you close this out?

Closing this one since it's false alarm.  Will create another bug to track the issue of identifying these dynamically switching GPUs.

I fail to see how this is a false alarm. I've confirmed this issue on my Mac Pro which does not have 2 GPUs as in the MacBook Pro mentioned in #66. Is a blacklist for pretty much all recent Macs the final answer on this?

Could you provide the about:gpu info from your Mac Pro?

At the moment we could do very little for all kinds of device/driver issues, unfortunately.  Hope we could provide a software rendering path soon.

Just to be clear, the cards we blacklisted on Mac is only a small portion.  For example, most NVIDIA cards works fine.

Initialization time	27
Vendor ID	0x1002
Device ID	0x9588
Driver Version	1.6.26
Pixel Shader Version	1.20
Vertex Shader Version	1.20
GL Version	2.1

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=76056

------------------------------------------------------------------------
r76056 | zmo@google.com | Fri Feb 25 09:14:39 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/resources/software_rendering_list.json?r1=76056&r2=76055&pathrev=76056

Add ATI Radeon HD 2600 XT on Mac to the software rendering list.

BUG= 68859 
TEST=none
TBR=vangelis@chromium.org

Review URL: http://codereview.chromium.org/6596010
------------------------------------------------------------------------

One thing you could try (and I'd very much like to see if it works or not) is to start chrome with --disable-gl-multisampling, and see if you still encounter the same problem.  If not, then we should turn off multisampling instead of turning of GPU.  Please let me know.

I tried --disable-gl-multisampling on my iMac with Radeon 2600 HD and it did not alleviate the crashing at http://www.doesmybrowsersupportwebgl.com/

did you try it with top of tree build?  --disable-gl-multisampling is not implemented in Chrome 9 or 10.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=78755

------------------------------------------------------------------------
r78755 | zmo@google.com | Fri Mar 18 13:59:48 PDT 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/resources/software_rendering_list.json?r1=78755&r2=78754&pathrev=78755

Update software rendering list:
(1) Since we disabled multisampling for ATI on Mac, remove a few Radeon cards from the list.
(2) Disable all GPU features for ATI on linux.
(3) Disable all GPU features for Intel on linux.

BUG= 73910 , 76428 , 76703 , 68859 
TEST=unittest

R=arv@chromium.org
Review URL: http://codereview.chromium.org/6713041
------------------------------------------------------------------------

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.