This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17423 - A way to destroy an AudioContext instance
Summary: A way to destroy an AudioContext instance
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: This bug has no owner yet - up for the taking
QA Contact: public-audio
Depends on:
Reported: 2012-06-05 15:52 UTC by olivier Thereaux
Modified: 2012-06-05 16:32 UTC (History)
0 users

See Also:


Description olivier Thereaux 2012-06-05 15:52:37 UTC
Closed per

Raised by Jussi as “There should be a way to destroy an Audio Context. This is especially important because the number of AudioContexts is limited, and if the end developer is using multiple libraries that create these contexts, this will be a problem unless the libraries have a way to get rid of the AudioContext instance. The ideal solution would be that AudioContexts would follow basic garbage collection rules and would be destroyed if there were no references to it, and currently the spec doesn't actually say anything about the garbage collection, so this is the expected behavior.”

Resolved at 16 Apr teleconference:

Resolution: close ISSUE-3 as satisfying as is, make sure we document limits in the number of contexts - not necessarily in the spec but in some developer doc.