Open Bug 1868256 Opened 1 year ago Updated 1 month ago

Crash in [@ mozilla::media::TimeUnit::MultDouble]

Categories

(Core :: Audio/Video: Playback, defect)

Unspecified
Android
defect

Tracking

()

Tracking Status
firefox-esr115 --- wontfix
firefox120 --- wontfix

People

(Reporter: mccr8, Unassigned)

References

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/98f955be-9c90-4d2c-9840-99e6f0231204

MOZ_CRASH Reason: MOZ_CRASH()

Top 10 frames of crashing thread:

0  libxul.so  mozilla::media::TimeUnit::MultDouble const  dom/media/TimeUnits.cpp:353
1  libxul.so  mozilla::Moof::Moof  dom/media/mp4/MoofParser.cpp:547
1  libxul.so  mozilla::MoofParser::RebuildFragmentedIndex  dom/media/mp4/MoofParser.cpp:71
2  libxul.so  mozilla::MoofParser::RebuildFragmentedIndex  dom/media/mp4/MoofParser.cpp:39
3  libxul.so  mozilla::MP4ContainerParser::ParseStartAndEndTimestamps  dom/media/mediasource/ContainerParser.cpp:544
4  libxul.so  mozilla::TrackBuffersManager::SegmentParserLoop  dom/media/mediasource/TrackBuffersManager.cpp:885
5  libxul.so  mozilla::detail::RunnableMethodArguments<>::apply<mozilla::TrackBuffersManager, void  const  xpcom/threads/nsThreadUtils.h:1164
5  libxul.so  std::__ndk1::__invoke_constexpr<mozilla::detail::RunnableMethodArguments<>::apply<mozilla::TrackBuffersManager, void   /builds/worker/fetches/android-ndk/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/c++/v1/type_traits:3880
5  libxul.so  std::__ndk1::__apply_tuple_impl<mozilla::detail::RunnableMethodArguments<>::apply<mozilla::TrackBuffersManager, void   /builds/worker/fetches/android-ndk/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/c++/v1/tuple:1415
5  libxul.so  std::__ndk1::apply<mozilla::detail::RunnableMethodArguments<>::apply<mozilla::TrackBuffersManager, void   /builds/worker/fetches/android-ndk/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/c++/v1/tuple:1424

An issue with this signature was fixed in bug 1845350, but it looks like it has started showing up on Android. I don't know if the volume is sufficient to be a problem, but I figured I'd file a new bug.

:padenot do you any insight why this might have come back? maybe bug 1839193?

Flags: needinfo?(padenot)

The crash rate was significant for a few days, but is low now.

Severity: -- → S3
Flags: needinfo?(padenot)
See Also: → 1989403
You need to log in before you can comment on or make changes to this bug.