After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764331 - GNOME Shell crashes Kernel (hard reset and reboot) in Chromium or Chrome
GNOME Shell crashes Kernel (hard reset and reboot) in Chromium or Chrome
Status: RESOLVED DUPLICATE of bug 762038
Product: gnome-shell
Classification: Core
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2016-03-29 19:13 UTC by CM
Modified: 2016-03-29 20:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Output of cat /var/log/kern.log when incident happened (1.04 KB, text/plain)
2016-03-29 19:13 UTC, CM
Details

Description CM 2016-03-29 19:13:47 UTC
Created attachment 324963 [details]
Output of cat /var/log/kern.log when incident happened

System setup:

- Intel dedicated hardware (Intel HD 4000, core i5 series, Intel NUC)
- UbuntuGNOME 15.10 and/or Ubuntu with GNOME 3.20.x (reproducible)
- Monitor connected to analog VGA port
- Chromium or Chrome installed



Problem:

Computer reboots when you start Chrome or Chromium on an external (VGA-connected) monitor, inspect the DOM of any web page and drag the node (drag&drop) and place it somewhere else.

The computer completely freezes (kernel freeze, no other TTY active) and needs to be hard-reset (10sec power shutdown).


How to reproduce:

- Start Chrome, Chromium or Opera
- Right Click / Inspect Element
- Move DOM node around via Drag&Drop (on the right side in Elements Tab)
- If Chrome window was on VGA monitor: Computer is now frozen and crashed.
- If Chrome window was on HDMI monitor: Computer did not freeze and works.


Further Debugging:

I have no clue on where to search for this bug or what is the real issue here. I bet that behaviour (that Apps so simply can totally kill the kernel) is not wanted anyhow, that's why I'm opening the issue here in the GNOME bugtracker.

This could be related to Chrome, Chromium as well, but I don't know if the Renderer behind the GNOME Shell is the cause of this.

The kernel log (attached), however, does not show much information at all. The only thing that's shown there is that gnome-shell.desktop was crashing, trapped and unrecoverable.


What can I do to get more information and data for this bug to help you?
Comment 1 Rui Matos 2016-03-29 20:14:13 UTC

*** This bug has been marked as a duplicate of bug 762038 ***