Crash in [@ mozilla::widget::GfxInfoBase::GetFeatureStatus]
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: gsvelto, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-83ef078d-e79a-4b13-8985-c7de70200624.
Top 10 frames of crashing thread:
0 XUL mozilla::widget::GfxInfoBase::GetFeatureStatus xpcom/ds/nsTArray.h:402
1 XUL gfxPlatform::InitAcceleration gfx/thebes/gfxPlatform.cpp:2557
2 XUL gfxPlatform::Init gfx/thebes/gfxPlatform.cpp:938
3 XUL mozilla::dom::ContentChild::RecvSetXPCOMProcessAttributes dom/ipc/ContentChild.cpp:638
4 XUL mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:10778
5 XUL mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2169
6 XUL mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1972
7 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1234
8 XUL mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
9 XUL MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
Low-volume crash, mostly happening on macOS. There's some older Windows reports but I don't think they're the same issue. This is a NULL-pointer dereference when accessing which seems to be happening within this call. Unfortunately the deep inlining of the implementation makes the stack not very helpful.
Comment 1•5 years ago
|
||
This probably fits better in the Graphics component.
Comment 2•5 years ago
|
||
GfxInfoBase::sFeatureStatus appears to be null. This should have been set in GfxInfoBase::SetFeatureStatus called by InitXPCOM before InitGraphicsDeviceData in ContentChild. I guess InitXPCOM must have early bailed on something almost catastrophic and a bunch of things didn't get initialized....
Comment 3•1 year ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•