1869713 - [gpu-canvas] crash on any canvas webpage (MakeCurrent called on a thread other than the creating thread)

Status: RESOLVED DUPLICATE of bug 1869818

(Core :: Graphics: Canvas2D, defect)

Description

[Mayank Bansal]

enable gpu-canvas
Go to https://www.w3schools.com/html/html5_canvas.asp

Crash : https://crash-stats.mozilla.org/report/index/7ef34804-d682-4180-a5b1-5972e0231213#tab-bugzilla
Alternate rare crash : https://crash-stats.mozilla.org/report/index/46d50a44-1626-4213-8e1c-759810231213#tab-bugzilla

Comment 1

[Mayank Bansal]

Attachment: about:support

Comment 2

[Mayank Bansal]

GP+[GFX1]: MakeCurrent called on a thread other than the creating thread!
(#39) GP+[GFX1]: Ignoring call to fDrawBuffers with failed mImplicitMakeCurrent.
(#40) GP+[GFX1]: MakeCurrent called on a thread other than the creating thread!
(#41) GP+[GFX1]: EGLContext#true is owned by/Current on thread#55032 but MakeCurrent requested on thread#56776!
(#42) GP+[GFX1]: Ignoring call to fReadBuffer with failed mImplicitMakeCurrent.
(#43) GP+[GFX1]: MakeCurrent called on a thread other than the creating thread!
(#44) GP+[GFX1]: EGLContext#true is owned by/Current on thread#55032 but MakeCurrent requested on thread#56776!
(#45) GP+[GFX1]: Ignoring call to fCheckFramebufferStatus with failed mImplicitMakeCurrent.
(#46) Error CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
(#47) Error CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
(#48) CP+[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
(#49) CP+[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
(#50) CP+[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
(#51) CP+[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
(#52) CP+[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
(#53) CP+[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1829026

Comment 4

[Mayank Bansal]

apart from the crash, the browser and/or the tabs also stop responding to user inputs. Windows may also show the "spinning circle" thingy.

Comment 5

[Takanori MATSUURA]

Dup. of bug 1869658?

Comment 6

[Lee Salzman [:lsalzman]]

This is not really supported or tested on Windows at all yet. Caveat emptor if you decide to enable it on Windows. But this is disabled by default.

Comment 7

[Mayank Bansal]

(In reply to Lee Salzman [:lsalzman] from comment #6)

This is not really supported or tested on Windows at all yet. Caveat emptor if you decide to enable it on Windows. But this is disabled by default.

Right. Which then means that till this crash is fixed there is no way to test gpu-canvas on Windows.
Edit: I have disabled gpu-canvas on Windows nightly, so the crash is 'fixed'. Feel free to RESOLVED FIXED etc.

Comment 8

[Mayank Bansal]

To avoid clutter, I will close this bug as INVALID and remove the regressed by bug. If/when windows support is actually developed, basic testing would catch this bug.

Comment 9

[Mayank Bansal]

Setting gfx.canvas.remote.worker-threads = 0 prevents the crashes
Briefly switching to d2d-canvas made me realize just how vastly superior gpu-canvas is. I would much rather prefer to continue to use gpu-canvas.