Closed Bug 1490462 Opened 6 years ago Closed 3 years ago

Fatal tab crash during multi-party WebRTC call

Categories

(Core :: WebRTC, defect, P2)

61 Branch
Desktop
macOS
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox62 - wontfix
firefox63 --- ?
firefox64 --- ?

People

(Reporter: rnewman, Unassigned)

References

Details

(Keywords: crash)

Crash Data

Perhaps similar to Bug 1409167. A content process crash a few minutes into a call in a closed-source UC system. https://crash-stats.mozilla.com/report/index/a8fd83c8-5729-4b26-9a62-51d4f0180906 abort rtc::FatalMessage::~FatalMessage() rtc::FatalMessage::~FatalMessage() webrtc::UpdateLogRatioMetric(webrtc::Stats*, float, float) webrtc::ProcessNearendBlock(webrtc::AecCore*, float*, float (*) [64], float (*) [64]) webrtc::WebRtcAec_ProcessFrames(webrtc::AecCore*, float const* const*, unsigned long, unsigned long, int, float* const*)
Crash Signature: [mozalloc_abort | abort | webrtc::UpdateLogRatioMetric] → mozalloc_abort | abort | webrtc::UpdateLogRatioMetric
Crash Signature: mozalloc_abort | abort | webrtc::UpdateLogRatioMetric → [@ mozalloc_abort | abort | webrtc::UpdateLogRatioMetric]
Probably one of the first two. It's also probably a NaN somewhere. Richard, what type of headset were you using during this call?
Flags: needinfo?(bugzilla)
Priority: -- → P2
This is low volume, not something we'd fix in a dot release.
(In reply to Paul Adenot (:padenot) from comment #2) > Richard, what type of headset were you using during this call? USB, either a Plantronics 628USB or a C520-M.
Flags: needinfo?(bugzilla)
QA Whiteboard: qa-not-actionable

Closing because no crashes reported for 12 weeks.

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