Issue metadata
Sign in to add a comment
|
Crash while trying to unlock the screen. |
||||||||||||||||||||
Issue descriptionIMPORTANT: Your crash has already been automatically reported to our crash system. Please file this bug only if you can provide more information about it. Chrome Version: 55.0.2883.42 Operating System: Linux 3.14.0 URL (if applicable) where crash occurred: Can you reproduce this crash? What steps will reproduce this crash? (If it's not reproducible, what were you doing just before the crash?) 1. 2. 3. ****DO NOT CHANGE BELOW THIS LINE**** Crash ID: crash/b1d42bcf00000000
,
Nov 28 2016
0x00007f5d15392dc0 (chrome -gl_context_egl.cc:132 ) gl::GLContextEGL::MakeCurrent
,
Dec 1 2016
Crash link to other cases of this: https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.magic_signature_1.name%3D%27gl%3A%3AGLContextEGL%3A%3AMakeCurrent%27&ignore_case=false crash rate appears to have peaked in 53 (54 counts are much lower). Still present in 56. Rare Windows cases as well - hard to tell if they're the same bug. Given the low rate, setting this to Pri2. We should bump priority if we see more of these in M55 stable.
,
Dec 9 2017
This bug has been quiet and looks unactionable. Possibly related: issue 720933 , issue 735508 Unlikely related: issue 791788
,
Dec 9 2017
Actually after a little digging there are a small number of these crashes still happening on ChromeOS: https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.magic_signature_1.name%3D%27gl%3A%3AGLContextEGL%3A%3AMakeCurrent%27%20AND%20product.name%3D%27Chrome_ChromeOS%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D They are mostly in the Intel driver. I'm going to reopen, attach this bug to that magic signature and unrestrict it.
,
Dec 9 2017
,
Jan 19 2018
If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jan 21
(2 days ago)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Nov 14 2016