No Luck, unable to reproduce the issue on Ubuntu 12.04 and Chrome: 35.0.1916.153.

Do you have any extensions installed ? If so, disable them and then give a try.

I disabled all the extensions, then went through re-enabling each one after locking the screen. No luck on a crash. I'll keep an eye out though.

Same version of xubuntu, same problem here... :(

same problem here on Ubuntu (Xubuntu) Linux + XFCE

Same problem here. Ubuntu with XFCE. I've noticed that if Chrome window is not set as active, it does not crash. 

Same problem. Xubuntu (xfce) 14.04.

I have the same problem mentioned above.

Chromium 37.0.2062.94
Xubuntu 14.04
 

Same here:

Version 37.0.2062.120 (64-bit)
Xubuntu 14.04.01, patched all the way to today.

I have noticed that this started to happen at some point, not really sure when. Most likely it was after an update of either Chrome or Xubuntu. It also got gradually worse. Now, I can reproduce it consistently every time: start chrome, lock, unlock, crash...

Same problem.

Chrome 37.0.2062.120 (64-bit)
Xubuntu 14.04

Same problem, Xubuntu 14.04.1 LTS, Chromium Version 37.0.2062.120 

Same problem here 
Xbuntu 14.04 Chromium version 37.0.2062.120

Same problem

Version 37.0.2062.120 (64-bit)
Xubuntu 14.04

Same configuration, same problem here.

Xubuntu 14.04 64-bit with google chrome stable 37.0.2062.120 (64-bit).
I lock and then unclock, puff "Google chrome has crashed" but dosen't actully crash.

No extensions installed, I actully removed google-chrome-beta because of this then installed a fresh stable in hopes this was only in beta. How wrong I was.

Something like this too, Version 37.0.2062.120 (64-bit), Xubuntu 14.04 patched to latest. Chrome freezes but I can close the window. Sometimes I get a message about a crash but which button I click on it seems to have no effect.

I just had this happen on a newly updated and restarted 38.0.2125.101 (64-bit)

Could it be related to the new screen locker in 14.04 switching VTs?http://xubuntu.org/news/screen-locking-in-xubuntu-14-04/

Has anybody tried removing lite-locker and installing xscreensaver instead?

I just tried replacing light-locker with xscreensaver and no more chromium crash. Thanks for the tip.

same issue with :
Version 38.0.2125.104 (64-bit)
xubuntu 14.04.1
light-locker 1.4.0

I'll try xscreensaver for the time being.

After a couple of hours, I confirm, no problem with xscreensaver instead of light-locker.
And just to clarify, it seems the crash is not always directly visible depending on people experiences :
- whoopsie notif
- windows black blink and some window rendering are wrong
- my personnal experience : the browser seems ok but sometimes windows rendering literally splash on the workspace I'm working on whereas no chrome windows is present on this particular workspace.

Same problem here:  
Version 38.0.2125.104 (64-bit)
Xubuntu 14.04

I just upgraded from 12.04.  Upon unlocking my screen the program reports that it has crashed.  Sometimes its still responsive afterwards, but most of the time it is totally frozen and I have to restart.  

I've even tried removing my .config/google-chrome/Default profile and rebuilding from scratch,  disabling extensions.  Problem remains.

Same problem here.  Sometimes I get a crash report.  Other times, all the tabs are frozen - clicking on the different tabs doesn't change the content of the screen.

Kernel: 3.13.0-39-generic x86_64
Xubuntu: 14.04.1 LTS
Chrome: 38.0.2125.111 (64-bit)

System is an upgrade from Xubuntu 13.10, where no problems were seen.

Exactly the same problem. After screen lock crash report and/or all the tabs are frozen.

Update:  I removed light locker and reinstalled xscreensaver.  The problem seems resolved now.  

Same problem with Lubuntu 14.04 (x86_64)

Kernel: 3.17.2-031702-generic #201410301416
Chrome: Version 39.0.2171.65 (64-bit)

Same issue in my desktop (64-bit) and laptop (using Chrome 32-bit) using Lubuntu 14.04.1 LTS and Chrome 39.0.2171.65 (64-bit on Desktop)


If Chrome isn't open as the main window this doesn't happen.

Same problem here:
Xubuntu 14.04.1 (amd64)
Chrome 40.0.2214.95-1 (amd64)
LightLocker 1.4.0-0ubuntu1 (amd64)

After screen lock i get frozen tabs or sometimes crash report.

I have the same problem with Lubuntu 14.04.1 i386, which also runs LightLocker rather than xscreensaver.  As others have reported, it is often the case that the browser remains functional even after the crash report.

I could have added (in #31) that I have seen this behavior on multiple machines.

I can confirm this.
Xubuntu 14.10 (amd64)
Chrome 40.0.2214.111 (amd64)

Frequent.

lenovo x230t
Ubuntu 14.04.1 LTS
Linux unknown 3.13.0-44-generic
xfce 4.10
chrome Version 41.0.2272.35 beta (64-bit)

Same here:
XFCE 4.10
Chrome Version 40.0.2214.111 (64-bit)

Linux 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

NAME="Ubuntu"
VERSION="14.04.1 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.1 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

Console output when this crash aoccurs:

[9628:9697:0221/120815:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 10000 ms.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[9094:9129:0221/130959:ERROR:channel.cc(258)] RawChannel read error (connection broken)

As already described, Chrome window stays open. Main menu can still be opened. When closing a tab, only the window title changes but the tab seems to stay open. Which is just a display error, because when restarting Chrome with 'restore tabs' option, the closed tabs do not appear.

14.04.1 LTS, Trusty Tahr
Linux ThinkPad 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Xfce 4.10
System: Lenovo ThinkPad L430
Chromium Version: Chromium 40.0.2214.111 Ubuntu 14.04

Had this problem with Xubuntu 14.04 and now with 14.10. Until recent updates I got a crash report but now it's just unresponsive for two-three minutes after logging in.

This just started happening to me today in Ubuntu 14.04 AFTER I installed other desktop environments -- Xubuntu, Lubuntu, Kubuntu (installed yesterday). I never saw this problem when I had only Unity/stock Ubuntu installed.

Based on a comment in another bug I turned OFF "Use hardware acceleration when available" in Chromium and so far it hasn't locked up since. (Still testing, though.)

Also tried to turn off "Use hardware acceleration when available" option. Works ok now.

All works fine after 2 days of testing. Seems that problem is realy in hardware acceleration.

Just got the repository upgrade to Chromium 41.0.2272.76 and turned on hardware acceleration... it still crashes.

I was experiencing this issue on Ubuntu 14.10 (as well as 14.04) running on Thinkpad X220 [1]. I was able to work around the issue by disabling Hardware acceleration. 

Based on a forum post about driver stability improvements [2], I installed the Intel video drivers from 01.org [3], and have been able to run Chromium successfully with Hardware acceleration turned on.

Hope this is helpful to others.

[1] http://www.thinkwiki.org/wiki/Category:X220
[2] http://askubuntu.com/a/584031
[3] https://01.org/linuxgraphics/

Using the cfg below, after a screen unlock, google-chrome has no response to mouse clicks, and when minimized and then restored, will not repaint its windows. HW acceleration is turned on; I'll try turning it off.

google-chrome Version 41.0.2272.89 (64-bit)
Linux 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 14.04.2 LTS

I'm not getting the crashes any more (since I switched back to
xscreensaver), but I am noticing window decorations (not the body) not
being repainted sometimes.

Google Chrome 41.0.2272.101
Linux 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux


David Knoll
*Developer*
*Future First*

[image: NEW LOGO SMALL]

020 7239 8933 | david@futurefirst.org.uk | www.futurefirst.org.uk |
@futurefirstorg

Future First, 338 City Road, London, EC1V 2PY

Future First is the public name for The Camden Future First Network, a
registered charity, number 1135638.

Standard disclaimer: this email and any attachments are confidential and
may also be privileged.  If you are not the addressee, do not disclose,
copy, circulate or in any other way use or rely on the information
contained in this email or any attachments.  If received in error, notify
the sender immediately and delete this email and any attachments from your
system.  Emails cannot be guaranteed to be secure or error free as the
message and any attachments could be intercepted, corrupted, lost, delayed,
incomplete or amended.  Future First does not accept legal responsibility
for the contents of this message or liability for damage caused by this
email or any attachments. Any views or opinions presented are only those of
the author and not those of Future First.

Same problem in Xubuntu 15.04 (upgraded from 14.10), but with a little change:
As soon as the light locker becomes active, chromium hangs in an endless loop. I can hear it because the CPU fan spins up. After unlocking, chromium shows a black window and I have to close or kill it, returning CPU load to zero.
Disabling hardware acceleration now to see if it helps.

Same problem with Ubuntu 14.10 & Chrome Version 43.0.2357.81 (64-bit)

same problem on fedora 21 and Chrome 43.0.2357.81 (64-bit)

Same problem on Arch linux with chrome version 45.0.2454.85 (64 bit)

same problem with ubuntu 14.04lts, chromium just udated, and amd64

same problem on fedora 21, chrome Version 46.0.2490.71 (64-bit)

Per #36 this could be GPU/GL related, passing to danakj@ for routing. This came to my attention as a top-starred Stability-Crash bug, see:

https://code.google.com/p/chromium/issues/list?can=2&q=label:Stability-Crash&sort=-stars&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified

with 45 stars. Note I am unable to repro locally on an Ubuntu 14.04 LTS with 48.0.2564.22.

[9628:9697:0221/120815:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 10000 ms.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[9094:9129:0221/130959:ERROR:channel.cc(258)] RawChannel read error (connection broken)

The gpu process hanging would cause it to eventually be killed (a crash) and restarted. Chrome should work normally after that happened.

People who are experiencing this crash, can you:
- Attach chrome's about:gpu page to this bug when it happens.
- Describe what video card and driver version you are using.

So far, I've seen mention of Intel in #43, and upgrading the driver from https://01.org/linuxgraphics/ fixed it.

Understanding how light-locker works (switching to a different VT), I think this is the same problem as https://code.google.com/p/chromium/issues/detail?id=355720 - i.e. GLX/DRI gets blocked by X when switching VTs, triggering the watchdog.

There are some interesting suggestions on that bug, so I will dup.