Ticket #1054 (closed bug: fixed)

Opened 3 years ago

Last modified 3 years ago

Cached MP3 files won't play in Mac Safari

Reported by: jeroen Owned by: pablo
Priority: Milestone: Flash 5.3
Component: Keywords:
Cc: ethan Forum thread:

Description

Steps to reproduce:

  1. Play an MP3 file, making sure it 's 100% loaded.
  2. Reload the page.
  3. Play again: nothing happens.

My guess is the player is internally waiting for a timed-out handler that sends a BUFFERCOMPLETE event or so. Because the file is cached, it is already completely loaded before the handler is called for the first time.

Change History

comment:1 Changed 3 years ago by pablo

I can't replicate this problem (FF 3.6 and Flash 10.1). I do notice however that in Firefox, there's a bit of a delay when the file is cached (during which _sound.bytesLoaded and bytesTotal are 0) where FF searches for the cached file. The same issue appears in previous versions of the player.

One workaround might be to use cache-busting on the sound files, but this may not be desirable behavior.

comment:2 Changed 3 years ago by jeroen

The issue is replicateable in Safari - FP10.1; the 5.2 player did not have this problem. I fear a race condition issue has been introduced.

comment:3 Changed 3 years ago by pablo

  • Summary changed from Cached MP3 files won't play to Cached MP3 files won't play in Mac Safari

OK, I have confirmed this in Safari. I'll look into it.

comment:4 Changed 3 years ago by pablo

Looks like this is related to a  bug in Flash on Safari, where sound.isBuffering is incorrectly reported as true. This only seems to happen if bufferLength is set. One workaround would be to eliminate the bufferLength property for mp3 files. Otherwise, we'll need to use another mechanism to detect buffering (although this leads to different problems, such as unknown durations, incorrect or incomplete bytesLoaded/bytesTotal information, etc).

comment:5 Changed 3 years ago by pablo

  • Status changed from new to closed
  • Resolution set to fixed

Addressed in 1328

comment:6 Changed 3 years ago by jeroen

Cool! However, next time it's a browser-plugin specific bug like that, I think we could just leave it. In this case I wondered if it was a manifestation of a wider race condition.

Note: See TracTickets for help on using tickets.