Closed Bug 968944 Opened 11 years ago Closed 9 years ago

Android crash in mozalloc_abort(char const*) | NS_DebugBreak | mozilla::layers::PLayerTransactionChild::Write - ABORT: actor has been |delete|d: file [...]/PLayerTransactionChild.cpp, line 3424

Categories

(Core :: Graphics: Layers, defect)

26 Branch
All
Android
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: kairo, Unassigned)

Details

(Keywords: crash, Whiteboard: [native-crash])

Crash Data

This bug was filed from the Socorro interface and is report bp-78e13b3e-09ff-459a-b506-447422140205. ============================================================= Top frames: 0 libmozalloc.so mozalloc_abort(char const*) memory/mozalloc/mozalloc_abort.cpp 1 libxul.so NS_DebugBreak xpcom/base/nsDebugImpl.cpp 2 libxul.so mozilla::layers::PLayerTransactionChild::Write(mozilla::layers::PCompositableChild*, IPC::Message*, bool) obj-firefox/ipc/ipdl/PLayerTransactionChild.cpp 3 libxul.so mozilla::layers::PLayerTransactionChild::Write(nsTArray<mozilla::layers::Edit> const&, IPC::Message*) obj-firefox/ipc/ipdl/PLayerTransactionChild.cpp 4 libxul.so mozilla::layers::PLayerTransactionChild::SendUpdateNoSwap(nsTArray<mozilla::layers::Edit> const&, mozilla::layers::TargetConfig const&, bool const&) obj-firefox/ipc/ipdl/PLayerTransactionChild.cpp 5 libxul.so mozilla::layers::ShadowLayerForwarder::EndTransaction(nsTArray<mozilla::layers::EditReply>*, bool*) gfx/layers/ipc/ShadowLayers.cpp 6 libxul.so mozilla::layers::ClientLayerManager::ForwardTransaction() gfx/layers/client/ClientLayerManager.cpp 7 libxul.so mozilla::layers::ClientLayerManager::EndTransaction(void (*)(mozilla::layers::ThebesLayer*, gfxContext*, nsIntRegion const&, mozilla::layers::DrawRegionClip, nsIntRegion const&, void*), void*, mozilla::layers::LayerManager::EndTransactionFlags) gfx/layers/client/ClientLayerManager.cpp 8 libxul.so nsDisplayList::PaintForFrame(nsDisplayListBuilder*, nsRenderingContext*, nsIFrame*, unsigned int) const layout/base/nsDisplayList.cpp 9 libxul.so nsDisplayList::PaintRoot(nsDisplayListBuilder*, nsRenderingContext*, unsigned int) const layout/base/nsDisplayList.cpp 10 libxul.so nsLayoutUtils::PaintFrame(nsRenderingContext*, nsIFrame*, nsRegion const&, unsigned int, unsigned int) layout/base/nsLayoutUtils.cpp The abort message is: xpcom_runtime_abort(###!!! ABORT: actor has been |delete|d: file /builds/slave/rel-m-rel-and_bld-000000000000/build/obj-firefox/ipc/ipdl/PLayerTransactionChild.cpp, line 3424) This is the #6 topcrash in early 27.0 release data on Android, looks like it has been around in 27 for a while but not in any significant manner in 26. The highest number of those are on Samsung devices but it affects all kind of other devices as well, with different Android versions (API level 12 and higher, I guess that means Honeycomb/3.0 and up). Graphics are different vendors and chips, no correlation. I also cannot see any URLs it would have any significant correlation with. More reports can be found under https://crash-stats.mozilla.com/report/list?signature=mozalloc_abort%28char%20const%2A%29%20%7C%20NS_DebugBreak%20%7C%20mozilla%3A%3Alayers%3A%3APLayerTransactionChild%3A%3AWrite%28mozilla%3A%3Alayers%3A%3APCompositableChild%2A%2C%20IPC%3A%3AMessage%2A%2C%20bool%29
Whiteboard: [native-crash]
I wonder if bug 940745 is the same crash? This one in Android, the bug 940745 in b2g?
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #1) > I wonder if bug 940745 is the same crash? This one in Android, the bug > 940745 in b2g? On b2g, it seems to be fixed by Bug 989408.
This crash still occurs but at extremely low volume: * 0 crashes with Fennec 41 * 6 crashes with Fennec 40 * 0 crashes with Fennec 34-39 * 96 crashes with Fennec 33 and earlier I'm resolving this bug as incomplete based on current crash rates. While there still seem to be rare cases where this occurs I don't believe its sufficient to warrant further investigation. Please reopen if you disagree.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.