New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 648767 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
█ kbr@chromium.org
█ xlai@chromium.org
xidac...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

DevTools causes crash in WebGL on tex-sub-image-2d-bad-args

Project Member Reported by kainino@chromium.org, Sep 20 2016 
Version: 55.0.2867.0 @ e0702d2 (and also 692194d, which is earlier)
OS: Ubuntu 14.04

What steps will reproduce the problem?
(1) Open conformance/textures/misc/tex-sub-image-2d-bad-args.html
(2) Open DevTools
(2.1) Add a breakpoint AFTER (not on) 120:
    gl.texImage2D(gl.TEXTURE_2D, 0, gl.RGBA, gl.RGBA, gl.UNSIGNED_BYTE, largeCanvas)
(3) Reload

What is the expected output?

No crash

What do you see instead?

Crash in rendering process
trace.txt
3.5 KB View Download

Comment 1 by kbr@chromium.org, Sep 20 2016

Cc: xlai@chromium.org junov@chromium.org xidac...@chromium.org
Components: Blink>Canvas
The crash is actually in Canvas2DLayerBridge:

[1:1:0920/150421:FATAL:Canvas2DLayerBridge.cpp(975)] Check failed: false. 

Not sure why that's getting triggered only when DevTools is open.

Comment 2 by xidac...@chromium.org, Sep 21 2016

Labels: Needs-Feedback
kainino@: I cannot repro this on ToT. I tried both Debug and Release version, and I can not repro the crash. Could you do a screenshot, and maybe also attach the chrome://gpu page?

Comment 3 by kainino@chromium.org, Sep 21 2016 

Took me a bit to repro this as well. Turns out I specifically had to have a breakpoint on any line AFTER line 120:

120   gl.texImage2D(gl.TEXTURE_2D, 0, gl.RGBA, gl.RGBA, gl.UNSIGNED_BYTE, largeCanvas);

And this reproduces the crash for me on a clean profile on ToT (878733d).
chrome-gpu.html
61.7 KB View Download

Comment 4 by kainino@chromium.org, Sep 21 2016

Description: Show this description

Comment 5 by kainino@chromium.org, Sep 21 2016

Description: Show this description

Comment 6 by junov@chromium.org, Sep 21 2016

Owner: junov@chromium.org
Status: Assigned (was: Untriaged)
I'll take this since the crash is most likely in code I wrote.

Comment 7 by junov@chromium.org, Sep 21 2016

Labels: -Needs-Feedback

Comment 8 by junov@chromium.org, Jul 25

Cc: -junov@chromium.org

Comment 9 by junov@chromium.org, Jul 25

Owner: ----
Status: Available (was: Assigned)
►

Sign in to add a comment