Closed Bug 1597854 Opened 5 years ago Closed 3 years ago

Crash in [@ mozilla::layers::AsyncImagePipelineManager::NotifyPipelinesUpdated]

Categories

(Core :: Graphics: WebRender, defect, P3)

72 Branch
x86_64
All
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox72 --- affected

People

(Reporter: mb8672, Unassigned)

References

Details

(Keywords: intermittent-failure)

Crash Data

This bug is for crash report bp-8408df47-981b-4f9f-b051-d62a50191120.

Top 10 frames of crashing thread:

0 XUL mozilla::layers::AsyncImagePipelineManager::NotifyPipelinesUpdated gfx/layers/wr/AsyncImagePipelineManager.cpp:533
1 XUL mozilla::wr::RenderThread::UpdateAndRender gfx/webrender_bindings/RenderThread.cpp:516
2 XUL mozilla::wr::RenderThread::HandleFrameOneDoc gfx/webrender_bindings/RenderThread.cpp:350
3 XUL mozilla::detail::RunnableMethodImpl<mozilla::wr::RenderThread*, void  xpcom/threads/nsThreadUtils.h:1176
4 XUL MessageLoop::DoWork ipc/chromium/src/base/message_loop.cc:523
5 XUL base::MessagePumpDefault::Run ipc/chromium/src/base/message_pump_default.cc:35
6 XUL MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
7 XUL base::Thread::ThreadMain ipc/chromium/src/base/thread.cc:192
8 XUL ThreadFunc ipc/chromium/src/base/platform_thread_posix.cc:40
9 libsystem_pthread.dylib _pthread_start 

Component: Graphics: Layers → Graphics: WebRender
Priority: -- → P3
OS: macOS → All
Depends on: 1696098

I wonder if there was a case that CompositorBridgeParent was destroyed without calling CompositorBridgeParent::ActorDestroy() nor WebRenderBridgeParent::Destroy(). It seems not happen when CompositorBridgeParent is alive.

See Also: → 1690752
Depends on: 1697090
Depends on: 1700848
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.