Open Bug 1886765 Opened 1 year ago Updated 2 months ago

Crash in [@ mozilla::wr::RenderThread::PostRunnable]

Categories

(Core :: Graphics, defect)

x86
Windows 7
defect

Tracking

()

People

(Reporter: sefeng211, Unassigned, NeedInfo)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/f3c49d85-331c-4bc7-b19f-e7fa60240305

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0  xul.dll  RefPtr<nsIThread>::get const  mfbt/RefPtr.h:325
0  xul.dll  RefPtr<nsIThread>::operator-> const  mfbt/RefPtr.h:355
0  xul.dll  mozilla::wr::RenderThread::PostRunnable  gfx/webrender_bindings/RenderThread.cpp:1166
0  xul.dll  mozilla::wr::RenderThread::PostEvent  gfx/webrender_bindings/RenderThread.cpp:686
0  xul.dll  mozilla::wr::WebRenderAPI::Create  gfx/webrender_bindings/WebRenderAPI.cpp:351
1  xul.dll  mozilla::layers::CompositorBridgeParent::AllocPWebRenderBridgeParent  gfx/layers/ipc/CompositorBridgeParent.cpp:1130
2  xul.dll  mozilla::layers::PCompositorBridgeParent::OnMessageReceived  ipc/ipdl/PCompositorBridgeParent.cpp:1248
3  xul.dll  mozilla::layers::PCompositorManagerParent::OnMessageReceived  ipc/ipdl/PCompositorManagerParent.cpp:194
4  xul.dll  mozilla::ipc::MessageChannel::DispatchAsyncMessage  ipc/glue/MessageChannel.cpp:1811
4  xul.dll  mozilla::ipc::MessageChannel::DispatchMessage  ipc/glue/MessageChannel.cpp:1736

This looks like a null pointer access. Definitely not new.

S3 as low crash volume.

Sotaro, it looks like we are failing to create the renderer thread (see the gfxCriticalError). Any ideas why that might be the case?

Can we do anything useful without a renderer thread? Should we just crash immediately if we fail to create one?

Severity: -- → S3
Flags: needinfo?(sotaro.ikeda.g)

Though the crash linked above is windows 7, there are some windows 10 and 11 crashes matching the signature

Failed to create Renderer thread: 0x8007000e

The above error means out of memory. Since almost all crashes happened with x86 Build Architecture, the thread creation failure seemed to happen more with x86.

When renderer thread creation fails, it seems better just to crash.

Currently, Firefox does not support Windows 7, so crashes are expected to gradually decrease.

Flags: needinfo?(sotaro.ikeda.g)

The bug is linked to a topcrash signature, which matches the following criteria:

  • Top 20 desktop browser crashes on beta (startup)
  • Top 5 desktop browser crashes on Windows on beta (startup)

:bhood, could you consider increasing the severity of this top-crash bug?

For more information, please visit BugBot documentation.

Flags: needinfo?(bhood)

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.

You need to log in before you can comment on or make changes to this bug.