W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Potential WebKit bug when using JavaScriptAudioNode

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 24 May 2012 12:06:22 +1200
Message-ID: <CAOp6jLadTbT8_cSc06DGk-uMBxUxzZ2KASecKgpnxE5NeE0nVA@mail.gmail.com>
To: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Cc: Colin Sullivan <colin@colin-sullivan.net>, public-audio@w3.org
On Thu, May 24, 2012 at 9:32 AM, Jussi Kalliokoski <
jussi.kalliokoski@gmail.com> wrote:

> I think this is because of garbage collection and it could be a bug either
> way. You have no static references (e.g. global scope) to the AudioContext
> or the nodes. That means that either the same buffer starting to repeat is
> the intended behavior and the timeout just gives the nodes a bit more
> lifetime, but the same behavior should occur after the timeout has been
> reached. The other option is that the intended behavior is that connected
> nodes aren't garbage collected. I'm not sure what is the current wanted
> behavior. I also think this might be the same bug as this:
> http://code.google.com/p/chromium/issues/detail?id=82795

A basic principle of Web API design is that GC doesn't affect application
output. That probably means connected nodes must not be garbage collected.

“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]
Received on Thursday, 24 May 2012 00:07:06 UTC

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