Closed Bug 1835760 Opened 2 years ago Closed 2 years ago

Crash in [@ mozilla::MediaDecoderStateMachine::DecodeMetadataState::HandleSeek]

Categories

(Core :: Audio/Video, defect)

Unspecified
All
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- unaffected
firefox114 --- unaffected
firefox115 + fixed
firefox116 + fixed

People

(Reporter: gsvelto, Assigned: padenot)

References

Details

(Keywords: crash, regression)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/f7624cd7-471e-47e1-bb8a-722380230529

MOZ_CRASH Reason: MOZ_DIAGNOSTIC_ASSERT(false) (Can't seek while decoding metadata.)

Top 10 frames of crashing thread:

0  libxul.so  mozilla::MediaDecoderStateMachine::DecodeMetadataState::HandleSeek  dom/media/MediaDecoderStateMachine.cpp:351
1  libxul.so  mozilla::MediaDecoderStateMachine::Seek  dom/media/MediaDecoderStateMachine.cpp:3866
2  libxul.so  mozilla::MediaDecoderStateMachineBase::InvokeSeek const  dom/media/MediaDecoderStateMachineBase.cpp:155
2  libxul.so  mozilla::detail::ProxyFunctionRunnable<mozilla::MediaDecoderStateMachineBase::InvokeSeek  xpcom/threads/MozPromise.h:1696
3  libxul.so  mozilla::AutoTaskDispatcher::TaskGroupRunnable::Run  xpcom/threads/TaskDispatcher.h:230
4  libxul.so  mozilla::TaskQueue::Runner::Run  xpcom/threads/TaskQueue.cpp:259
5  libxul.so  nsThreadPool::Run  xpcom/threads/nsThreadPool.cpp:343
6  libxul.so  nsThread::ProcessNextEvent  xpcom/threads/nsThread.cpp:1234
7  libxul.so  NS_ProcessNextEvent  xpcom/threads/nsThreadUtils.cpp:479
7  libxul.so  mozilla::ipc::MessagePumpForNonMainThreads::Run  ipc/glue/MessagePump.cpp:300

This appears to be an Android-specific regression, the first affected build ID is 20230518092544.

It's not Android-specific, it seems to be happening on Windows too.

OS: Android → All
See Also: → 1835763

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 AArch64 and ARM crashes on nightly

For more information, please visit BugBot documentation.

Keywords: topcrash
Assignee: nobody → padenot

This bug has been marked as a regression. Setting status flag for Nightly to affected.

:jimm could this be triaged for Priority/Severity?
We tracked this for 115 since it's a new crash

Flags: needinfo?(jmathies)

Setting 115 to fixed, the crash was addressed in Fx115 and is being investigated with release asserts in nightly

Flags: needinfo?(jmathies)

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.

Keywords: topcrash

anything left to do here for fx116?

Flags: needinfo?(padenot)

I don't think so.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(padenot)
Resolution: --- → FIXED
See Also: → 1844478
You need to log in before you can comment on or make changes to this bug.