Closed
Bug 1869932
Opened 5 months ago
Closed 2 months ago
Crash in [@ mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::ipc::IProtocol::FatalError | mozilla::dom::PWebrtcGlobalParent::OnMessageReceived]
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox122 | --- | affected |
People
(Reporter: release-mgmt-account-bot, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/92169722-08f9-40e0-adbd-449fc0231212
MOZ_CRASH Reason: MOZ_CRASH(IPC FatalError in the parent process!)
Top 10 frames of crashing thread:
0 libxul.so mozilla::ipc::FatalError ipc/glue/ProtocolUtils.cpp:209
1 libxul.so mozilla::ipc::IProtocol::HandleFatalError ipc/glue/ProtocolUtils.cpp:440
2 libxul.so mozilla::ipc::IProtocol::FatalError ipc/glue/ProtocolUtils.cpp:431
2 libxul.so mozilla::dom::PWebrtcGlobalParent::OnMessageReceived ipc/ipdl/PWebrtcGlobalParent.cpp:487
3 libxul.so mozilla::dom::PContentParent::OnMessageReceived ipc/ipdl/PContentParent.cpp:6764
4 libxul.so mozilla::ipc::MessageChannel::DispatchAsyncMessage ipc/glue/MessageChannel.cpp:1813
4 libxul.so mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:1732
4 libxul.so mozilla::ipc::MessageChannel::RunMessage ipc/glue/MessageChannel.cpp:1525
4 libxul.so mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1623
5 libxul.so mozilla::RunnableTask::Run xpcom/threads/TaskController.cpp:549
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2023-10-18
- Process type: Parent
- Is startup crash: No
- Has user comments: No
- Is null crash: Yes - 2 out of 3 crashes happened on null or near null memory address
Updated•5 months ago
|
Component: General → WebRTC
Reporter | ||
Comment 1•5 months ago
|
||
The severity field is not set for this bug.
:mjf, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(mfroman)
Updated•5 months ago
|
Flags: needinfo?(mfroman) → needinfo?(jib)
Comment 2•5 months ago
|
||
There's no actual webrtc tree code in this stack. Just generated code:
auto maybe__stats = IPC::ReadParam<nsTArray<RTCStatsReportInternal>>((&(reader__))); if (!maybe__stats) { FatalError("Error deserializing 'RTCStatsReportInternal[]'");
WebRTC Stats reports happen at a regular cadence whenever WebRTC is in use, so they might just be victims of OOM.
Reporter | ||
Comment 3•2 months ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•