New issue
Advanced search Search tips

Issue 763038 link

Starred by 1 user
Status: WontFix
Owner:
hongchan@chromium.org
Closed: Oct 15
Cc:
binji@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

WebAudio AudioBuffers should be detachable

Project Member Reported by binji@chromium.org, Sep 7 2017 
Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
(1) Create an AudioBuffer from an AudioContext
(2) Get the ChannelData from the AudioBuffer
(3) Attempt to transfer the buffer

What is the expected result?

The buffer is detached.

What happens instead?

The buffer data is copied but the buffer is not detached.

Comment 1 by rtoy@chromium.org, Sep 8 2017

Cc: -rtoy@chromium.org
 Issue 761801  has a good example of the failure to detach.
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 10

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by hongchan@chromium.org, Oct 15

Cc: binji@chromium.org
Owner: hongchan@chromium.org
binji@

https://jsfiddle.net/3kq9xfb8/

Now I get 0 from ArrayBuffer from AudioBuffer.getChannelData() after the transfer. Seems like the issue is fixed?

Comment 4 by hongchan@chromium.org, Oct 15

Labels: -Hotlist-Recharge-Cold
Use this link instead: https://jsfiddle.net/1j8wdtxh/

Comment 5 by hongchan@chromium.org, Oct 15

Status: Unconfirmed (was: Untriaged)

Comment 6 by binji@google.com, Oct 15 

I didn't look too closely, but it seems that this is the correct behavior.

Comment 7 by hongchan@chromium.org, Oct 15

Status: WontFix (was: Unconfirmed)
binji@ Thanks! I am closing this as WontFix.
►

Sign in to add a comment