W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: ScriptProcessorNode behavior without JavsScript references

From: Chris Wilson <cwilso@google.com>
Date: Wed, 18 Sep 2013 06:38:32 -0700
Message-ID: <CAJK2wqWGhNSDwZNdk4MybMJixT3jw3FcSBk+=uxCYPioGerH2A@mail.gmail.com>
To: Marcus Geelnard <mage@opera.com>
Cc: Raymond Toy <rtoy@google.com>, "Robert O'Callahan" <robert@ocallahan.org>, "public-audio@w3.org" <public-audio@w3.org>
On Wed, Sep 18, 2013 at 6:26 AM, Marcus Geelnard <mage@opera.com> wrote:

>  That sounds like a reasonable solution (or it could just disconnect
> itself?).

Yes, presumably you could just disconnect yourself, and that would cause
the onaudioprocess to stop being called (and thus release observability).

In any event I think that we need to clearly instruct developers to signal
> the death of ScriptProcessorNodes, or they could leak like mad (e.g. if you
> create one ScriptProcessorNode per note played in a MIDI application).

Yep, that's the major concern here.  I foresee LOTS of leaky SP scenarios.

> One way could be to add an explicit "active" attribute to the node or
> something (that would be hard to miss for developers).

But they won't be checking them - because they won't have references
anymore.  :)

Received on Wednesday, 18 September 2013 13:38:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:25 UTC