ended event may not always be fired

NEW
Unassigned

Status

()

defect
P3
normal
3 years ago
3 years ago

People

(Reporter: jya, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox46 affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Posted file nspr.log
Spawned From bug 1229987 comment 43.

If the video track is slightly longer than the audio track, the MDSM may stop requesting video frames from the reader and never detects that it's EOS.

Causing the event to never be fired.

The log attached shows that the MDSM has requested the exact number of frames available but didn't continue to receive the EOS signal.
(Reporter)

Updated

3 years ago
Attachment #8699847 - Attachment mime type: text/x-log → text/html
(Reporter)

Updated

3 years ago
Summary: ended event may not always fire → ended event may not always be fired
(Reporter)

Updated

3 years ago
Attachment #8699847 - Attachment mime type: text/html → text/plain
(Reporter)

Updated

3 years ago
See Also: → 1229987
(Reporter)

Comment 1

3 years ago
the log was created by using the MediaFormatReader:5 NSPR_MODULES_LOG.

The right timing condition was created by delaying audio decoding (using mediasource and only feeding some audio) and letting it play until the waiting event is fired.

We then add a little bit more video and end the mediasource.

ended event should always fire per spec
It would be nice to have a test case to repro the problem.
(Reporter)

Comment 3

3 years ago
(In reply to JW Wang [:jwwang] from comment #2)
> It would be nice to have a test case to repro the problem.

once bug 1229987 land, dom/media/mediasource/test/test_WaitingToEndedTransition_mp4.html will cause about 25% failure rate on win7 debug.

unfortunately, it's all timing related, and I've never been able to reproduce the problem locally.

What I can reproduce often however is that the waiting event is not always fired when you would expect it to (which is at worse the start time of the last audio frame). Yet I see waiting event sometimes fired 65ms earlier.
(Reporter)

Comment 4

3 years ago
here is one run.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=cafb2714a9a3

win8 debug run was 76% failure rate, however I only re-ran the try 5 times ... 
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e2b7518507ae
Priority: -- → P2
Mass change P2 -> P3
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.