1134125 - A buffer will be empty when AudioContext#decodeAudioData

Status: RESOLVED INVALID

(Core :: Web Audio, defect)

Description

[Yonamine Nao]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36

Steps to reproduce:

var audioContext = new AudioContext();
var audioData = new Uint8Array(128).buffer;

// expect byteLength is 128
console.log(audioData.byteLength);

audioContext.decodeAudioData(audioData, function() {});

// expect byteLength is 128, but got 0.
console.log(audioData.byteLength);


Actual results:

audioData.byteLength is 0.


Expected results:

audioData.byteLength is 128.

Comment 1

[Loic]

Regression range:
good=2014-05-22
bad=2014-05-23
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b40296602083&tochange=e9b2b72f4e6c

Alice, any idea about the regression bug?

Comment 2

[Alice0775 White]

Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=78bc7d04bac9&tochange=e08a482fcead

Suspect: Bug 1007223 and Bug 989921

Comment 3

[Loic]

Thanks. CC'ing Paul for more info.

Comment 4

[Paul Adenot (:padenot)]

This is the behavior that is required per spec, other browsers might or might not implement it correctly.

This is step 3 of the algorithm at [0]. Neutering means the buffer should now has a size of 0, its content should not be available anymore to the page.

I'm closing this, as we are clearly doing the right stuff. Yonamine Nao, maybe you can file a bug at other browser vendors' bug tracker ?

[0]: http://webaudio.github.io/web-audio-api/#widl-AudioContext-decodeAudioData-Promise-AudioBuffer--ArrayBuffer-audioData-DecodeSuccessCallback-successCallback-DecodeErrorCallback-errorCallback