Re: Proposal for fixing race conditions from Jer Noble on 2013-07-18 (public-audio@w3.org from July to September 2013)

From: Jer Noble <jer.noble@apple.com>
Date: Thu, 18 Jul 2013 12:05:14 -0700
To: Ehsan Akhgari <ehsan.akhgari@gmail.com>
Cc: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>, Marcus Geelnard <mage@opera.com>, WG <public-audio@w3.org>, "robert@ocallahan.org" <robert@ocallahan.org>, "K. Gadd" <kg@luminance.org>, Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>
Message-id: <E9411661-7937-4290-94BD-B5D7957B5A0D@apple.com>

On Jul 18, 2013, at 12:03 PM, Ehsan Akhgari <ehsan.akhgari@gmail.com> wrote:

> Hmm, the original ArrayBuffer will get GCed if the content code is not holding on to it, right?  And if they are, that is memory that the content is keeping alive.  Surely we're not trying to solve the problem of making it impossible for content to write code which results in an OOM, etc., right?  Or am I missing something?

At some future date, yes.  In the current WebKit implementation, you will see a severe "sawtooth" memory useage.  Doubling the live buffer size will make those "teeth" taller between GCs.

-Jer

Received on Thursday, 18 July 2013 19:05:45 UTC