Issue metadata
Sign in to add a comment
|
Tiles start turning black, then display in the wrong place, then Chrome gets killed by SIGILL
Reported by
jasper...@gmail.com,
Oct 30 2016
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36 Steps to reproduce the problem: 1. Use Chrome as normal for an extended period of time What is the expected behavior? Chrome works like it should. What went wrong? Tiles go black, display in the wrong place, and eventually Chrome gets killed. System logs show Chrome got killed by SIGILL. I will add a screenshot the next time it happens. Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes Chrome version: 54.0.2840.71 Channel: stable OS Version: Fedora 24 Flash Version: Shockwave Flash 23.0 r0 Disabling hardware acceleration doesn't fix the issue, neither does disabling the accelerated 2D canvas flag. It happens on both Xwayland and X. I'm using a Lenovo X220 laptop with an Intel Core i5-2520M with integrated graphics.
,
Oct 31 2016
Tested the issue on Fedora 22 Desktop and could not reproduce the issue. Could some one from MTV team please look into the issue and update. Thank You.
,
Nov 4 2016
,
Nov 7 2016
jasper26v@, can you please upgrade to the latest stable build [54.0.2840.90] available & check if you still come across this issue ?
,
Nov 10 2016
I've been using Chrome for about three hours straight right now, and it's still up and running as normal. Before this it would crash approximately every 30 minutes, so I think we can conclude this issue is fixed. Thanks for the good work!
,
Nov 11 2016
Thank you jasper26v@ for the update. Marking this Bug as Wont Fix as per # 5. Please file a new issue if you come across this again. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by jasper...@gmail.com
, Oct 30 2016