This bug was filed from the Socorro interface and is report bp-79e2a5d8-2063-4c9d-9022-c1de02150213. ============================================================= Currently at #26 in the "Top Crashers for Firefox 36.0b" list, with 1803 crashes in the past week in that channel (I suspect the real number is higher). All crashes are on Windows. A couple of user comments mentions "Youtube video". Stack: mozalloc_abort(char const* const) mozalloc_handle_oom(unsigned int) moz_xrealloc nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_CopyWithMemutils>::EnsureCapacity(unsigned int, unsigned int) nsTArray_Impl<mozilla::ContextStateTracker::ContextState, nsTArrayInfallibleAllocator>::AppendElement<mozilla::ContextStateTracker::ContextState&>(mozilla::ContextStateTracker::ContextState&) mp4_demuxer::Index::Index(stagefright::Vector<stagefright::MediaSource::Indice> const&, mp4_demuxer::Stream*, unsigned int, __int64, mozilla::Monitor*) mp4_demuxer::MP4Demuxer::Init()
[Tracking Requested - why for this release]: topcrash
tracking-firefox36: --- → ?
tracking-firefox37: --- → ?
tracking-firefox38: --- → ?
The crash is with an older 36 beta build that I think still has MSE enabled. I'm going to assume that 37+ is affected but am not sure that 36 is affected as we disabled MSE. Ralph - Can you add this to your MSE queue for investigation?
status-firefox36: --- → ?
status-firefox37: --- → affected
status-firefox38: --- → affected
tracking-firefox36: ? → -
tracking-firefox37: ? → +
tracking-firefox38: ? → +
Hmm. Build ID is 20150209164123 which sounds like beta 8. I disabled MSE for 36 on February 5th (bug 1129039) so I would expect MSE to be off by then. In any case, we need to find out whether this is resolved. Tracking for MSE until we do. Syd, can you take a look at the crashstats and see if we're still getting this with more recent 36 builds?
Flags: needinfo?(giles) → needinfo?(spolk)
Priority: -- → P1
36.0b8 (buildId 20150209164123): Plenty but none after 2015-02-19 36.0b9 (buildId 20150212154903): Happened 1554 times since 2015-02-12 (release date) Happened 128 times since 2015-02-25 36.0b10 (buildId 20150217132925): 0 times 37.0b1 (buildId 20150223185154): 0 times Looks like the fix made it into 36.0b10.
Great, thanks Syd. We'll watch this for another week as 37b1 gets distributed.
I don't see any instance of this on 37 beta1. I am going to resolve fix and we can reopen if it surfaces again.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Updating status flags as per comment 6.
status-firefox36: affected → fixed
status-firefox37: affected → fixed
status-firefox38: affected → fixed
You need to log in before you can comment on or make changes to this bug.