Open
Bug 712792
Opened 13 years ago
Updated 3 years ago
Shutdown hang with nsBuiltinDecoderStateMachine::StopAudioThread
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
NEW
People
(Reporter: Felipe, Unassigned)
Details
Attachments
(1 file)
146.16 KB,
application/octet-stream
|
Details |
Webm video had stopped working on this session: the video progress would show as loaded, but pressing play would not work. This was true both for a webm video embedded in youtube's page, or for standalone webm file loaded on a tab.
Then I tried to quit Firefox and it stuck hung on shutdown eating 63% of the CPU.
I attached MSVC2010 and one of the threads had the following stack:
xul.dll!nsThread::ProcessNextEvent(bool mayWait=true, bool * result=0x30a5f653) Line 596 + 0x4 bytes C++
xul.dll!NS_ProcessNextEvent_P(nsIThread * thread=0x090e9860, bool mayWait=true) Line 245 + 0xd bytes C++
xul.dll!nsThread::Shutdown() Line 502 + 0xa bytes C++
xul.dll!nsBuiltinDecoderStateMachine::StopAudioThread() Line 1185 C++
xul.dll!nsBuiltinDecoderStateMachine::DecodeSeek() Line 1459 C++
xul.dll!nsBuiltinDecoderStateMachine::DecodeThreadRun() Line 442 + 0x6 bytes C++
xul.dll!nsRunnableMethodImpl<void (__thiscall nsBuiltinDecoder::*)(void),1>::Run() Line 346 C++
xul.dll!nsThread::ProcessNextEvent(bool mayWait=true, bool * result=0x090e9801) Line 666 C++
xul.dll!nsThreadStartupEvent::Run() Line 221 + 0x8 bytes C++
nspr4.dll!_PR_NativeRunThread(void * arg=) Line 448 C
msvcr80.dll!_getptd_noexit() Line 633 + 0x7 bytes C
nspr4.dll!pr_root(void * arg=0x0996b5c0) Line 122 + 0xd bytes C
msvcr80.dll!_callthreadstartex() Line 348 + 0x6 bytes C
msvcr80.dll!_threadstartex(void * ptd=0x1003ad08) Line 326 + 0x5 bytes C
kernel32.dll!@BaseThreadInitThunk@12() + 0x12 bytes
ntdll.dll!___RtlUserThreadStart@8() + 0x27 bytes
ntdll.dll!__RtlUserThreadStart@8() + 0x1b bytes
This seems very similar to bug 687709 but since that is about StopDecodeThread and this is StopAudioThread I'm filing them separately. Feel free to mark as dup.
I got both a minidump (attached), an xperf -on latency output (50mb), and a minidump with heap (727mb) if that would help.
Xperf didn't provide much insight AFAICT, lots of unknown symbols and the typical thread starvation signs (GetCurrentThread etc.): http://i.imgur.com/TJVgI.png
Comment 1•13 years ago
|
||
What page/video did this happen with, and do you have a way to reproduce it?
Comment 2•13 years ago
|
||
Felipe ?
Updated•10 years ago
|
Component: Audio/Video → Audio/Video: Playback
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•