- From: Chris Wilson <cwilso@google.com>
- Date: Fri, 29 Aug 2014 12:28:18 -0700
- To: "www-tag@w3.org List" <www-tag@w3.org>
- Message-ID: <CAJK2wqXhJ6YpryRSrocSug4z2VwCabkbUwyDp3LchYgiU6MKXQ@mail.gmail.com>
Hello TAG! We're discussing an issue in the Web Audio API ( https://github.com/WebAudio/web-audio-api/issues/317) of the need for suspending and resuming AudioContexts for power consumption reasons. Alongside this, we've found the need to be able to release AudioContexts completely - in short, AudioContexts may be consuming system resources, and we need a way for developers to definitively state "I'm done with this now", aside from just releasing references and hoping the GC takes care of it. The current proposal <http://cwilso.github.io/web-audio-api/proposals.html#widl-AudioContext-release-Promise> is to add a method to the AudioContext interface: Promise release (); Releases the audio context, including any system resources used by it. This will not automatically release all AudioContext-created objects, unless other references have been released as well; however, it will forcibly release any system resources that might prevent additional AudioContexts from being created and used. The promise resolves when any AudioContext-creation-blocking resources have been released. Do you have any concerns over this pattern? Thanks, -Chris
Received on Friday, 29 August 2014 19:28:45 UTC