Crash in [@ mozilla::media::Interval<T>::Interval<T> | mozilla::TrackBuffersManager::RemoveFrames]
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox130 | --- | wontfix |
firefox131 | --- | wontfix |
firefox132 | --- | wontfix |
People
(Reporter: gsvelto, Assigned: karlt)
References
(Depends on 2 open bugs, Blocks 1 open bug, Regression)
Details
(Keywords: crash, regression)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/3c5447a0-6d6c-442c-8b2b-1dc740240824
MOZ_CRASH Reason: MOZ_DIAGNOSTIC_ASSERT(mStart <= mEnd) (Invalid Interval)
Top 10 frames:
0 xul.dll mozilla::media::Interval<mozilla::media::TimeUnit>::Interval<mozilla::media::... dom/media/Intervals.h:48
1 xul.dll mozilla::TrackBuffersManager::RemoveFrames(mozilla::media::TimeIntervals cons... dom/media/mediasource/TrackBuffersManager.cpp:2637
2 xul.dll mozilla::TrackBuffersManager::InsertFrames(nsTArray<RefPtr<mozilla::MediaRawD... dom/media/mediasource/TrackBuffersManager.cpp:2395
3 xul.dll mozilla::TrackBuffersManager::ProcessFrames(nsTArray<RefPtr<mozilla::MediaRaw... dom/media/mediasource/TrackBuffersManager.cpp:2284
4 xul.dll mozilla::TrackBuffersManager::CompleteCodedFrameProcessing() dom/media/mediasource/TrackBuffersManager.cpp:1829
5 xul.dll RefPtr<mozilla::TrackBuffersManager>::assign_assuming_AddRef(mozilla::TrackBu... mfbt/RefPtr.h:65
5 xul.dll RefPtr<mozilla::TrackBuffersManager>::operator=(void*) mfbt/RefPtr.h:180
5 xul.dll mozilla::MozPromise<RefPtr<mozilla::MediaTrackDemuxer::SamplesHolder>, mozill... xpcom/threads/MozPromise.h:746
6 xul.dll mozilla::MozPromise<bool, mozilla::MediaResult, 1>::ThenValueBase::DoResolveO... xpcom/threads/MozPromise.h:621
6 xul.dll mozilla::MozPromise<bool, mozilla::MediaResult, 1>::ThenValueBase::ResolveOrR... xpcom/threads/MozPromise.h:488
This is an assertion that was introduced in bug 1530322 but started triggering relatively recently. The oldest build IDs that appear in this crash signature are 20240710091735 for beta and 20240728093905 for nightly. It's odd that we started seeing the crash in beta slightly before nightly, but it's possible that the bug was triggered by a change that was quickly uplifted. It would be interesting to know what are the values of mStart
and mEnd
, I'll have a look if I can retrieve them from a minidump.
Updated•1 month ago
|
Assignee | ||
Comment 1•1 month ago
|
||
Thanks! Since the fix for bug 1906667, this is tracking the more recent and more frequent crash seen in bug 1906088.
Comment 2•1 month ago
|
||
Set release status flags based on info from the regressing bug 1903974
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•7 days ago
|
Description
•