Open Bug 1595458 Opened 2 months ago Updated 2 months ago

Crash in [@ mozilla::ipc::MessageChannel::CxxStackFrame::CxxStackFrame | mozilla::ipc::MessageChannel::Send | mozilla::ipc::IProtocol::ChannelSend]

Categories

(Core :: Panning and Zooming, defect, P3)

x86_64
Linux
defect

Tracking

()

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-fcfa1346-ad76-481c-a72a-4c2a60191110.

Top 10 frames of crashing thread:

0 libxul.so mozilla::ipc::MessageChannel::CxxStackFrame::CxxStackFrame ipc/glue/MessageChannel.cpp:228
1 libxul.so mozilla::ipc::MessageChannel::Send ipc/glue/MessageChannel.cpp:999
2 libxul.so mozilla::ipc::IProtocol::ChannelSend ipc/glue/ProtocolUtils.cpp:477
3 libxul.so mozilla::layers::PAPZParent::SendDestroy ipc/ipdl/PAPZParent.cpp:356
4 libxul.so mozilla::layers::CompositorBridgeParent::LayerTreeState::~LayerTreeState gfx/layers/ipc/CompositorBridgeParent.cpp:235
5 libxul.so std::_Rb_tree<mozilla::layers::LayersId, std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState>, std::_Select1st<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> >, std::less<mozilla::layers::LayersId>, std::allocator<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> > >::_M_erase /builds/worker/fetches/clang/include/c++/7.4.0/bits/stl_tree.h:1858
6 libxul.so std::_Rb_tree<mozilla::layers::LayersId, std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState>, std::_Select1st<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> >, std::less<mozilla::layers::LayersId>, std::allocator<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> > >::_M_erase /builds/worker/fetches/clang/include/c++/7.4.0/bits/stl_tree.h:1856
7 libxul.so std::_Rb_tree<mozilla::layers::LayersId, std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState>, std::_Select1st<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> >, std::less<mozilla::layers::LayersId>, std::allocator<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> > >::_M_erase /builds/worker/fetches/clang/include/c++/7.4.0/bits/stl_tree.h:1856
8 libxul.so std::_Rb_tree<mozilla::layers::LayersId, std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState>, std::_Select1st<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> >, std::less<mozilla::layers::LayersId>, std::allocator<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> > >::_M_erase /builds/worker/fetches/clang/include/c++/7.4.0/bits/stl_tree.h:1856
9 libxul.so std::_Rb_tree<mozilla::layers::LayersId, std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState>, std::_Select1st<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> >, std::less<mozilla::layers::LayersId>, std::allocator<std::pair<mozilla::layers::LayersId const, mozilla::layers::CompositorBridgeParent::LayerTreeState> > >::_M_erase /builds/worker/fetches/clang/include/c++/7.4.0/bits/stl_tree.h:1856

The raw crash reason is MOZ_RELEASE_ASSERT(mWorkerThread == GetCurrentVirtualThread())

https://hg.mozilla.org/mozilla-central/annotate/caf55914ccddba34d462a1206530d7868b6c4992/ipc/glue/MessageChannel.cpp#l228

Crashes are coming from Fedora, Arch and Ubuntu so it's not a distro-specific thing.

Component: Graphics: Layers → Panning and Zooming
Priority: -- → P3

Volume increased a lot starting with the 20191120215217 build, and this is also happening on windows.

Changing the priority to p2 as the bug is tracked by a release manager for the current nightly.
See What Do You Triage for more information

Priority: P3 → P2

The recent spike is possibly related to canvas 2d remoting, which is now disabled again.

Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.