Here's a video that shows the problem: https://www.youtube.com/watch?v=74sB1-8tAdA

Can you run your browser without libva libraries ? I don't think it is a libva related issue if you can't find any error in /sys/class/drm/card0/error.

Hi @haiho,

Sorry, I am very new to the Linux graphics stack.

Do you by any chance know how can I run Chrome without libva libraries? I have just recently learned a tiny bit about Linux graphics and it is very confusing to me: mesa, gallium, xv, gl, va, drm, dri (?), etc. etc.

Should I just temporarily uninstall the libva libraries? Or does Chrome accept a commandline flag to disable i t?

Cheers,
Behrang

Please uninstall the libva libraries fist then run Chrome.

You were right. It was not due to the libva libaries.

Last night I reinstalled my system on a new SSD that I had got and it only had this libva:

libva1:amd64 1.6.0-1

Removing that also removed:

libavcodec-ffmpeg56:amd64 7:2.7.6-0ubuntu0.15.10.1

However I could reproduce the issue by just opening and closing Chrome multiple times. Last time I opened it, it froze the whole system with the exception of the mouse:

Here's a photo I took from the monitor when this happened:

https://dl.dropboxusercontent.com/u/34024/Ubuntu%2015.10%20Chrome%20Crash/Chrome%20Crash%20under%20Ubuntu%2015.10%20-%20with%20markers.png

Chrome pops up an invisible rectangle for a few seconds and then the borders of the rectangle remains on the screen but other than that everything freezes.

Could you please let me know what should I be looking at next?

Created attachment 121763 [details]
When the screen freezes with Chrome's "invisible window" marked with markers

Created attachment 121764 [details]
Contains two log files (chrome_debug-freeze.log and chrome_debug-no-freeze.log)

I ran Chrome with the following logging/debugging flags to see if I can see anything particularly suspicious:

--enable-logging 
--v=1 
--enable-gpu-service-tracing 
--enable-gpu-client-tracing 
--log-gpu-control-list-decisions 
--enable-extension-activity-logging 
--enable-gpu-command-logging

I have attached two files, one called chrome_debug-freeze.log and one called chrome_debug-no-freeze.log.

The first one contains logging information gathered when Chrome froze the whole system as soon as I opened it.

The second one contains logging information for a non freezing Chrome session (having said that, sometimes Chrome starts properly and then crashes while watching a video, etc.)

Both logs contain heaps of ERRORs. However here's a grep for ERROR on the chrome_debug-freeze.log file:

[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetBucketSize
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetBucketData
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetToken
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetBucketSize
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetBucketData
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: SetToken
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [GroupMarkerNotSet(crbug.com/242999)!:C8E010ACA0030000]cmd: kTraceBeginCHROMIUM
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [.CompositorWorker-0x2747f4e11580]cmd: SetBucketSize
[6427:6427:0216/005403:ERROR:gles2_cmd_decoder.cc(4577)] [.CompositorWorker-0x2747f4e11580]cmd: SetBucketSize

I will share this bug report with the Chrome team as well. Most of the errors seem to be related to OpenGL ES 2.0, but I am not sure if Chrome is using this (https://code.google.com/archive/p/gles2-bc/) version of gles2 or another implementation.

List of potentially related packages:

* libegl1-mesa/wily,now 11.0.2-1ubuntu4
* libgl1-mesa-dri/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libgl1-mesa-glx/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libglapi-mesa/wily,now 11.0.2-1ubuntu4 amd64 [installed,automatic]
* libglew1.10/wily,now 1.10.0-3 amd64 [installed,automatic]
* libglewmx1.10/wily,now 1.10.0-3 amd64 [installed,automatic]
* libglib2.0-0/wily,now 2.46.1-1 amd64 [installed,automatic]
* libglib2.0-bin/wily,now 2.46.1-1 amd64 [installed,automatic]
* libglib2.0-data/wily,now 2.46.1-1 all [installed,automatic]
* libglibmm-2.4-1v5/wily,now 2.45.41.is.2.44.0-0ubuntu2 amd64 [installed,automatic]
* libglu1-mesa/wily,now 9.0.0-2 amd64 [installed,automatic]
* libcogl-common/wily,now 1.20.0-2 all [installed,automatic]
* libcogl-pango20/wily,now 1.20.0-2 amd64 [installed,automatic]
* libcogl-path20/wily,now 1.20.0-2 amd64 [installed,automatic]
* libcogl20/wily,now 1.20.0-2 amd64 [installed,automatic]

The bug reported in Chromium: https://code.google.com/p/chromium/issues/detail?id=586926

So it isn't a libva issue, I will closed it as 'notourbug'. Please file a new bug to ask helps from graphics guys if you think your issue is related to OpenGL ES.

Isn't it possible to change the product field?

Yes, you can change the product field. But I was thinking the first comments might confuse others.

Which product should I use? Can't see anything OpenGL related.

According to report's new comment, this isn't a libva issue and might be related to OpenGL.

One way that I could reproduce this issue was by opening and closing Chrome multiple times in a row and suddenly my whole system freezes.

Here are some Chrome specific command-line flags that might come in handy when trying to find the issue:

--blacklist-accelerated-compositing 
--blacklist-webgl 
--disable-accelerated-2d-canvas 
--disable-accelerated-compositing 
--disable-accelerated-layers 
--disable-accelerated-video 
--disable-accelerated-video-decode 
--disable-gpu 
--disable-gpu-compositing 
--disable-gpu-driver-bug-workarounds 
--disable-gpu-process-prelaunch 
--disable-gpu-program-cache 
--disable-gpu-rasterization 
--disable-gpu-shader-disk-cache 
--disable-gpu-vsync 
--disable-gpu-watchdog 
--disable-map-image 
--disable-threaded-compositing 
--log-gpu-control-list-decisions 
--disable-accelerated-fixed-root-background 
--disable-accelerated-overflow-scroll 
--disable-pinch 
--disable-universal-accelerated-overflow-scroll 
--disable-webrtc-hw-decoding 
--disable-webrtc-hw-encoding 
--enable-deferred-filters 

I have also reported the bug to Chromium's bug tracker and some communication with them might help fix this issue sooner rather than later:

https://code.google.com/p/chromium/issues/detail?id=586926