Closed Bug 948155 Opened 11 years ago Closed 6 years ago

some mp3s continue to play after reaching the reported duration with DirectShow backend

Categories

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

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: rowbot, Unassigned)

References

()

Details

(Keywords: regression)

good: 2013-12-04
bad: 2013-12-05

Suspected: Bug 945947 - Re-enable DirectShow for MP3 playback on Vista and later

When you play this file at the linked URL it reports that it has a duration of 5:29, which is the correct duration.  However, once the current time reaches the reported duration of 5:29, the current time and duration begin incrementing in sync.  This happened until the duration reached about 9:50 when the media finally ceased playback and an |ended| event was fired.  Chrome, Safari, and IE do not exhibit this behavior.  An example of what happens is as follows:

Current Time / Duration
0:00 / 5:29
0:01 / 5:29
0:02 / 5:29
...
5:27 / 5:29
5:28 / 5:29
5:29 / 5:29
5:30 / 5:30
5:31 / 5:31
5:32 / 5:32
...
9:49 / 9:49
9:50 / 9:50

Out of curiosity I attached a |durationchange| event to the media player.  Once the current time and duration synced up, my browser was spammed with over 6600 |durationchange| events before playback ended.
Keywords: regression
Version: 28 Branch → Trunk
Confirmed 29.0a1 (2013-12-15), win 7 x64.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: Audio/Video → Audio/Video: Playback
Mass closing do to inactivity.
Feel free to re-open if still needed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
Thanks for poking this bug. I totally forgot about it. The behavior I was seeing seems to have been fixed by a commit on 2015-10-02. Bug 1209410 seems like the likely culprit for resolving this. Here is the push log, unfortunately mozregression couldn't narrow it down any further:

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5f16c6c2b969f70e8da10ee34853246d593af412&tochange=d1c5a7c5b4331ee9ea5443de893fcfd0a5b80e2a
You need to log in before you can comment on or make changes to this bug.