573026 - ASSERTION: Should have positive frame time: 'videoData->mTime >= mStartTime'

Status: RESOLVED WORKSFORME

(Core :: Audio/Video, defect)

Description

[Boris Zbarsky [:bzbarsky]]

I ran into this assert when running something totally unrelated on try server.  It fired during the running of layout/generic/crashtests/493111-1.html, which doesn't even include any video stuff...

Comment 1

[Boris Zbarsky [:bzbarsky]]

Oh, and the file+line, on a build from yesterday, is:

file /builds/slave/tryserver-linux-debug/build/content/base/src/nsContentUtils.cpp, line 2719

Comment 2

[Justin Wood (:Callek)]

And hit on SeaMonkey Cd in a test that also does not have any video stuff [crashtests/489462-1.html].

###!!! ASSERTION: Should have positive frame time: 'videoData->mTime >= mStartTime', file e:/builds/slave/comm-central-trunk-win32-debug/build/mozilla/content/media/nsBuiltinDecoderStateMachine.cpp, line 1115
gklayout!nsBuiltinDecoderStateMachine::Run+0x00000000000003E0 (e:\builds\slave\comm-central-trunk-win32-debug\build\mozilla\content\media\nsbuiltindecoderstatemachine.cpp, line 807)
xpcom_core!nsThread::ProcessNextEvent+0x00000000000001FA (e:\builds\slave\comm-central-trunk-win32-debug\build\mozilla\xpcom\threads\nsthread.cpp, line 547)
xpcom_core!NS_ProcessNextEvent_P+0x0000000000000053 (e:\builds\slave\comm-central-trunk-win32-debug\build\objdir\mozilla\xpcom\build\nsthreadutils.cpp, line 250)
xpcom_core!nsThread::ThreadFunc+0x00000000000000CE (e:\builds\slave\comm-central-trunk-win32-debug\build\mozilla\xpcom\threads\nsthread.cpp, line 263)
nspr4!_PR_NativeRunThread+0x00000000000000DB (e:\builds\slave\comm-central-trunk-win32-debug\build\mozilla\nsprpub\pr\src\threads\combined\pruthr.c, line 426)
nspr4!pr_root+0x0000000000000019 (e:\builds\slave\comm-central-trunk-win32-debug\build\mozilla\nsprpub\pr\src\md\windows\w95thred.c, line 122)

Comment 6

[Jesse Ruderman]

This orange is hard-to-star because it happens after the video-using crashtest has finished.

Comment 7

[Matthew Gregan [:kinetik]]

This assertion still exists, but presumably hasn't caused test orange for a long time.  Marking this WFM on the assumption that a bug fix solved this.