Crash when rendering WebGL KIP |
|||
Issue descriptionChromeOS version: 65.0.3325.209 (Stable) 66.0.3359.158 (Stable) 67.0.3381.0 (Dev) ChromeOS device model: KIP HP Chromebook 11 G4/G4 EE Case#: 16048818 Description: Devices are shutting down and they are not able to recover when running websites that use WebGL. Steps to reproduce: go to https://web.basemark.com/ Current Behavior / Reproduction: They get a black color screen and sometime devices restart to the sign in screen Expected Behavior: Device should be able to finish the test Drive link to logs: debug logs: https://drive.google.com/open?id=11TMgjnIf_OZuGSZ5ED2T69mYAumoB7SO customer info: https://drive.google.com/open?id=1alSARSaTzpZ9X4jdlhRMH9-ZoLTjP5e2bTT-M6lz0-Q video of the issue: https://drive.google.com/open?id=1uMjodFDDL8Lz8DgXkE478EHA3rJlEB-c chrome://gpu (G3): https://drive.google.com/open?id=1BaBviYP3dpHU6Z0spYvYtXFRzmI_DZ45 chrome://gpu (G4): https://drive.google.com/open?id=13h1MwsMxl14npTRhJVNwCoW4K7llxw0v I don't have this HW so I can't reproduce. in the log I see: [4478:4478:0611/132327.593604:ERROR:gles2_cmd_decoder.cc(7645)] [.Offscreen-For-WebGL-0x358ff4392400]GL ERROR :GL_INVALID_OPERATION : glClear: can't be called on integer buffers [4478:4478:0611/132329.655517:ERROR:gles2_cmd_decoder.cc(10002)] [.Offscreen-For-WebGL-0x358ff4392400]RENDER WARNING: there is no texture bound to the unit 1 and in the messages 2018-06-11T13:22:34.729278-05:00 INFO kernel: [ 187.185534] Watchdog[1394]: segfault at 0 ip 00005a092311f7a7 sp 00007817d77a1a00 error 6 in chrome[5a091f5b1000+8511000] 2018-06-11T13:23:05.503959-05:00 INFO kernel: [ 218.009395] Watchdog[4438]: segfault at 0 ip 000055d6f67a07a7 sp 00007c754ae7aa00 error 6 in chrome[55d6f2c32000+8511000] 2018-06-11T13:23:48.305859-05:00 INFO kernel: [ 260.880533] Watchdog[4481]: segfault at 0 ip 00005734c15aa7a7 sp 00007e087abb8a00 error 6 in chrome[5734bda3c000+8511000] but there are no crash_ID.
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Dec 14
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 20
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information. |
|||
►
Sign in to add a comment |
|||
Comment 1 by kbr@chromium.org
, Jun 25 2018Owner: ihf@chromium.org