1267931 - crash in shutdownhang | mozilla::WMFMediaDataDecoder::ProcessFlush()

Status: RESOLVED DUPLICATE of bug 1274498

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

Description

[JW Wang [:jwwang] [:jw_wang]]

This bug was filed from the Socorro interface and is 
report bp-936734a4-0018-499f-b9f0-e4d012160426.
=============================================================

Thread 50, 57, 60, 62, 64, 65, 67
mozilla::WMFMediaDataDecoder::ProcessFlush()
Not sure if these threads are stuck in ProcessFlush().

Thread 44, 46, 47, 48, 51, 52, 54, 56
mozilla::WMFMediaDataDecoder::Flush()
It is interesting the number of threads that are calling Flush() do not equal the number of threads that are calling ProcessFlush().

Comment 1

[Jean-Yves Avenard [:jya]]

(In reply to JW Wang [:jwwang] from comment #0)
Thread 50, 57, 60, 62, 64, 65, 67
> mozilla::WMFMediaDataDecoder::ProcessFlush()
> Not sure if these threads are stuck in ProcessFlush().
> 
> Thread 44, 46, 47, 48, 51, 52, 54, 56
> mozilla::WMFMediaDataDecoder::Flush()
> It is interesting the number of threads that are calling Flush() do not
> equal the number of threads that are calling ProcessFlush().

Flush will be called on the reader's taskqueue.

ProcessFlush runs on the MediaDataDecoder FlushableTaskQueue

So ProcessFlush threads will never match the one of Flush (and it's the same with most MediaDataDecoder implementations)