Closed Bug 1612801 Opened 4 years ago Closed 3 years ago

Crash in [@ mozilla::HostWebGLContext::HostWebGLContext]

Categories

(Core :: Graphics: CanvasWebGL, defect, P2)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox75 --- wontfix
firefox76 --- wontfix
firefox77 --- affected

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-92fa857f-0751-479a-a921-fb15b0200130.

Top 10 frames of crashing thread:

0 xul.dll mozilla::HostWebGLContext::HostWebGLContext dom/canvas/HostWebGLContext.cpp:69
1 xul.dll static mozilla::HostWebGLContext::Create dom/canvas/HostWebGLContext.cpp:60
2 xul.dll static mozilla::dom::WebGLParent::Create dom/canvas/WebGLParent.cpp:25
3 xul.dll mozilla::layers::ContentCompositorBridgeParent::AllocPWebGLParent gfx/layers/ipc/ContentCompositorBridgeParent.cpp:773
4 xul.dll mozilla::layers::PCompositorBridgeParent::OnMessageReceived ipc/ipdl/PCompositorBridgeParent.cpp:2656
5 xul.dll mozilla::layers::PCompositorManagerParent::OnMessageReceived ipc/ipdl/PCompositorManagerParent.cpp:498
6 xul.dll mozilla::ipc::MessageChannel::DispatchSyncMessage ipc/glue/MessageChannel.cpp:2183
7 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2132
8 xul.dll mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:2006
9 xul.dll MessageLoop::DoWork ipc/chromium/src/base/message_loop.cc:523

This looks like a NULL-pointer dereference happening here. The oldest buildid showing this crash is 20200129213721.

There appear to be only two users affected ATM, they are both using nVidia cards.

Component: Graphics → Canvas: WebGL

This in the remote-ipc-webgl codepaths, and shouldn't be possible to hit. But I don't see the pref in question in the crashes, weird.

Priority: -- → P2

This is the top non-hang, non-OOM|small crash on the April 23 Windows Nightly, with 26 crashes.

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.