User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101116 Firefox/4.0b8pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101116 Firefox/4.0b8pre dont play audio file in the browser. the same thing happen with video like this and other websites: http://edn.embarcadero.com/kr/article/40914 Reproducible: Always

I'm able to reproduce this on Win 7, the error console has something like this: Error: [Exception... "'Error: NS_ERROR_UNKNOWN_HOST' when calling method: [nsIStreamListener::onStopRequest]" nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "<unknown>" data: no]

They are not using HTML5 to play the audio, it might be a plugin issue, assuming they're using flash or somesuch to play the audio.

Midaired. Actually, this page seems to be using Flash, and the error message in comment #1 doesn't reproduce when clicking on the "Listen" button. This must be something else. I was not able to reproduce this problem on Mac with the latest version of the nightly and the latest version of Flash. I'm trying to find a regression window.

The google translate example works in 11/10 and fails on 11/11: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=df1d1ff6b489&tochange=0f17e5f1eb01 There are many things there including some plugins patches. So I will move there for now.

Regression range: Works: http://hg.mozilla.org/mozilla-central/rev/212a391d3b79 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101109 Firefox/4.0b8pre ID:20101110052514 Fails: http://hg.mozilla.org/mozilla-central/rev/bdbef533364f Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101109 Firefox/4.0b8pre ID:20101110081923 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=212a391d3b79&tochange=bdbef533364f

dup of 601064?

Seems like it, although plugin layers apparently made it worse?

ooops... sorry guys

(In reply to comment #9) > > *** This bug has been marked as a duplicate of bug 601064 *** No regression range is different REOPENED

The symptoms and the fix will be the same. We probably just caused it to happen in more cases on the new date.