Closed Bug 1297148 Opened 8 years ago Closed 1 year ago

Crash in mozilla::CrossProcessMutex::CrossProcessMutex


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

48 Branch



Tracking Status
firefox48 - wontfix
firefox49 --- wontfix
fennec + ---
firefox50 --- wontfix
firefox51 --- fix-optional
firefox52 --- fix-optional
firefox53 --- fix-optional


(Reporter: u279076, Unassigned)



(Keywords: crash, regression, Whiteboard: [gfx-noted])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-56652f58-d463-4e07-8a8d-86ffc2160804.
0 	mozilla::CrossProcessMutex::CrossProcessMutex 	ipc/glue/CrossProcessMutex_posix.cpp:63
1 	mozilla::layers::AsyncPanZoomController::ShareCompositorFrameMetrics 	gfx/layers/apz/src/AsyncPanZoomController.cpp:3747
2 	mozilla::layers::AsyncPanZoomController::NotifyLayersUpdated 	gfx/layers/apz/src/AsyncPanZoomController.cpp:3267
3 	mozilla::layers::APZCTreeManager::PrepareNodeForLayer 	gfx/layers/apz/src/APZCTreeManager.cpp:463
4 	mozilla::layers::APZCTreeManager::UpdateHitTestingTree 	gfx/layers/apz/src/APZCTreeManager.cpp:571
5 	mozilla::layers::APZCTreeManager::UpdateHitTestingTree 	gfx/layers/apz/src/APZCTreeManager.cpp:602
6 	mozilla::layers::APZCTreeManager::UpdateHitTestingTree 	gfx/layers/apz/src/APZCTreeManager.cpp:602
7 	mozilla::layers::APZCTreeManager::UpdateHitTestingTree 	gfx/layers/apz/src/APZCTreeManager.cpp:602
8 	mozilla::layers::APZCTreeManager::UpdateHitTestingTree 	gfx/layers/apz/src/APZCTreeManager.cpp:182
9 	mozilla::layers::CompositorBridgeParent::ShadowLayersUpdated 	gfx/layers/ipc/CompositorBridgeParent.cpp:1398
10 	mozilla::layers::LayerTransactionParent::RecvUpdate 	gfx/layers/ipc/LayerTransactionParent.cpp:633
11 	mozilla::layers::LayerTransactionParent::RecvUpdateNoSwap 	gfx/layers/ipc/LayerTransactionParent.cpp:207
12 	mozilla::layers::PLayerTransactionParent::OnMessageReceived 	obj-firefox/ipc/ipdl/PLayerTransactionParent.cpp:538
13 	mozilla::layers::PCompositorBridgeParent::OnMessageReceived 	obj-firefox/ipc/ipdl/PCompositorBridgeParent.cpp:521
14 	mozilla::ipc::MessageChannel::DispatchAsyncMessage 	ipc/glue/MessageChannel.cpp:1654
15 	mozilla::ipc::MessageChannel::DispatchMessage 	ipc/glue/MessageChannel.cpp:1592
16 	mozilla::ipc::MessageChannel::OnMaybeDequeueOne 	ipc/glue/MessageChannel.cpp:1559
17 	MessageLoop::RunTask 	ipc/chromium/src/base/
18 	MessageLoop::DeferOrRunPendingTask 	ipc/chromium/src/base/
19 	MessageLoop::DoWork 	ipc/chromium/src/base/
20 	base::MessagePumpDefault::Run 	ipc/chromium/src/base/
21 	MessageLoop::Run 	ipc/chromium/src/base/
22 	base::Thread::ThreadMain 	ipc/chromium/src/base/
23 	ThreadFunc 	ipc/chromium/src/base/
Ø 24 	
Ø 25 	
Ø 26 	
Ø 27 	
More reports:

Originally saw this when investigating bug 1038253, it looks like there is a spike in these crashes with Fennec 48 beginning on August 3, 2016. By volume this is low at #292 (0.04%). There does not appear to be a strong device or Android version correlation.

[Tracking Requested - why for this release]: Flagging merely because it appears to be a regression in 48.
Component: Graphics: Layers → Panning and Zooming
It looks like the shared memory is failing to be allocated (OOM) or get mapped (out of file descriptors?). One possible short term solution is to not use the cross process mutex on Android and instead use a regular mutex not allocated from shared memory since Fennec is currently single process with multiple threads. However once we enable either compositor process or e10s, we would need to use the cross process mutex again. Of course finding a way to share the FrameMetrics with out having to lock a piece of shared memory would be even better.
Regression from APZ in 48. Marking P3 since the crash volume seems pretty low.
tracking-fennec: ? → +
This is a very low volume crash so right now there are no reports in 52. There are two reports in 51 though so marking that as affected. It's quite likely still affecting 52 but we just haven't gotten any reports of it yet.
This crash is present in 49.0.2, but it looks as there isn't yet any volume in 50 (12 crashes in B12) and only a few crashes in Aurora. Maybe not worth tracking any longer?
Severity: critical → S2

This is very low volume, <10 crashes in all of 2022, the newest version we have a crash in is 92. Decreasing severity -> S3.

Severity: S2 → S3
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.