Crash in [@ libc.so.6 | libc.so.6 | libc.so.6 | mozilla::ipc::MessageChannel::WaitForSyncNotify | mozilla::ipc::MessageChannel::Send | mozilla::ipc::IProtocol::ChannelSend | mozilla::layers::PCompositorBridgeChild::SendWillClose]
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox144 | --- | unaffected |
| firefox145 | --- | unaffected |
| firefox146 | --- | fixed |
People
(Reporter: release-mgmt-account-bot, Assigned: emilio)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(1 file)
Crash report: https://crash-stats.mozilla.org/report/index/cd9e314a-ce0b-4165-be80-a42ab0251031
Reason: SIGABRT
Top 10 frames of crashing thread:
0 libc.so.6 libc.so.6@0x7a982
1 libc.so.6 libc.so.6@0x6f2ab
2 libc.so.6 libc.so.6@0x7197d
3 firefox-bin mozilla::detail::ConditionVariableImpl::wait mozglue/misc/ConditionVariable_posix.cpp:104
3 firefox-bin mozilla::detail::ConditionVariableImpl::wait_for mozglue/misc/ConditionVariable_posix.cpp:111
4 libxul.so mozilla::OffTheBooksCondVar::Wait xpcom/threads/CondVar.h:65
4 libxul.so mozilla::Monitor::Wait xpcom/threads/Monitor.h:39
4 libxul.so mozilla::ipc::MessageChannel::WaitForSyncNotify ipc/glue/MessageChannel.cpp:1842
4 libxul.so mozilla::ipc::MessageChannel::Send ipc/glue/MessageChannel.cpp:1337
4 libxul.so mozilla::ipc::IProtocol::ChannelSend ipc/glue/ProtocolUtils.cpp:500
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2025-10-31
- Process type: Parent
- Is startup crash: No
- Has user comments: No
- Is null crash: No
By analyzing the backtrace, the regression may have been introduced by a patch [1] to fix Bug 1994879.
[1] https://hg.mozilla.org/mozilla-central/rev?node=8c5286558339
:jswinarton, since you are the author of the potential regressor, could you please take a look?
Comment 1•6 months ago
|
||
I think these patches were authored by :emilio.
| Assignee | ||
Comment 2•6 months ago
|
||
It runs script at a time when APZ holds locks. It seems notifying this
through the event loop shouldn't cause any adverse effect (and in fact
is already the case for the GPU process).
Updated•6 months ago
|
| Reporter | ||
Comment 4•6 months ago
|
||
Copying crash signatures from duplicate bugs.
| Assignee | ||
Updated•6 months ago
|
| Reporter | ||
Comment 6•6 months ago
|
||
Copying crash signatures from duplicate bugs.
Comment 8•6 months ago
|
||
| bugherder | ||
Updated•6 months ago
|
Updated•5 months ago
|
Description
•