GPU process crashes on some sites
Reported by
zet...@gmail.com,
Feb 28 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2657.0 Safari/537.36 Steps to reproduce the problem: 1. Open chrome://gpu. All is ok! 2. Open random site, for example https://www.moedelo.org/buro-authorization/ 3. All Software only or Unavaible What is the expected behavior? GPU acceleration working for all types. What went wrong? GPU process crashed chrome://gpu when something went wrong with process. https://gist.github.com/zetoke/cb0aa75744c38630186e Did this work before? N/A Chrome version: 50.0.2657.0 Channel: n/a OS Version: Flash Version:
,
Feb 28 2016
https://player.spotify.com affected
,
Feb 28 2016
With nouveau drivers its all ok! Problem only with Nvidia proprietary driver 361.28 (Arch linux)
,
Mar 2 2016
zetoke@ Are you seeing this issue on other latest chrome channels like Beta or stable? If crashes are seen again please provide the crash ID's from chrome://crashes. It will be helpful to triage further.
,
Mar 2 2016
brajkumar@ I see this issue on all versions: Chromium Stable, Chrome Stable, Chrome Beta, Chrome Dev. Also, on Blink-based browsers: Opera and Vivaldi. I recorded a screencast with an error: https://www.youtube.com/watch?v=rem0fCxjXDc Also, crash IDs with error on video-try: Crash ID aaecd59800000000 (Chrome) Crash ID 9bf477d400000000 (Chrome) Crash ID 13d0e9f000000000 (Chrome)
,
Mar 2 2016
Another crash on maps.google.com May be related Screencast: https://www.youtube.com/watch?v=xb0Sd1muNT8 Crash ID 290fd59800000000 (Chrome)
,
Mar 2 2016
I'm find temp solution from this bugreport: https://bugs.chromium.org/p/chromium/issues/detail?id=575548 At comment 5. --disable-gpu-sandbox flag working for me too
,
Mar 9 2016
Thank you for providing more feedback. Assigning to requester "brajkumar@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 28 2016
This crash is being investigated in 482198 , hence duping. |
||||
►
Sign in to add a comment |
||||
Comment 1 by zet...@gmail.com
, Feb 28 2016