Closed Bug 1720586 Opened 5 years ago Closed 4 years ago

Crash in [@ abort | webrtc::UpdateLogRatioMetric]

Categories

(Core :: WebRTC, defect)

Firefox 92
x86_64
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr78 --- unaffected
firefox90 --- unaffected
firefox91 --- unaffected
firefox92 --- affected

People

(Reporter: alex_mayorga, Unassigned)

Details

(Keywords: crash, nightly-community, Whiteboard: [not-a-fission-bug])

Crash Data

Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/c4a2bcc3-15e2-4007-841c-4fa900210714

Reason: STATUS_STACK_BUFFER_OVERRUN / FAST_FAIL_FATAL_APP_EXIT

Top 10 frames of crashing thread:

0 ucrtbase.dll abort 
1 xul.dll rtc::FatalMessage::~FatalMessage third_party/libwebrtc/webrtc/rtc_base/checks.cc:69
2 xul.dll webrtc::UpdateLogRatioMetric third_party/libwebrtc/webrtc/modules/audio_processing/aec/aec_core.cc:454
3 xul.dll webrtc::ProcessNearendBlock third_party/libwebrtc/webrtc/modules/audio_processing/aec/aec_core.cc:1458
4 xul.dll webrtc::WebRtcAec_ProcessFrames third_party/libwebrtc/webrtc/modules/audio_processing/aec/aec_core.cc:1932
5 xul.dll webrtc::WebRtcAec_Process third_party/libwebrtc/webrtc/modules/audio_processing/aec/echo_cancellation.cc:350
6 xul.dll webrtc::EchoCancellationImpl::ProcessCaptureAudio third_party/libwebrtc/webrtc/modules/audio_processing/echo_cancellation_impl.cc:176
7 xul.dll webrtc::AudioProcessingImpl::ProcessCaptureStreamLocked third_party/libwebrtc/webrtc/modules/audio_processing/audio_processing_impl.cc:1213
8 xul.dll webrtc::AudioProcessingImpl::ProcessStream third_party/libwebrtc/webrtc/modules/audio_processing/audio_processing_impl.cc:873
9 xul.dll mozilla::AudioInputProcessing::PacketizeAndProcess dom/media/webrtc/MediaEngineWebRTCAudio.cpp:1061
Severity: -- → S2

Only one crash report so far.

Whiteboard: [not-a-fission-bug]

This doesn't look like a Fission crash, even though the crash report in comment 0 has DOMFissionEnabled=1.

We're missing a line of the stack where ProcessNearendBlock calls UpdateMetrics, so we don't have info on which of the 3 calls to UpdateLogRatioMetric might have caused the actual crash here. We'd need that to know which of the denominator params passed into UpdateLogRatioMetric was negative. Each of those fields (nearLevel, lineoutLevel, and nlpoutLevel) are PowerLevels.

It seems like a PowerLevel shouldn't be negative, but this is new code to me. padenot, do you have any thoughts here?

Flags: needinfo?(padenot)

I'm thinking with this code changing when we land the libwebrtc uplift soon, and that we only have one crash on record, this can probably be downgraded to an S3. We can move it back if it becomes more prevalent.

Severity: S2 → S3

I agree with the assessment in comment 3.

Flags: needinfo?(padenot)

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.