From c63a89e7accd08f9f89570af4992e5b7c9c63580 Mon Sep 17 00:00:00 2001 From: joeberkovitz Date: Fri, 3 Mar 2017 12:54:31 -0500 Subject: [PATCH 1/3] Clarify normative aspects of AudioNode lifetime. --- index.html | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/index.html b/index.html index c829a6e15..54b4a6ac5 100644 --- a/index.html +++ b/index.html @@ -3088,21 +3088,21 @@

-

+

Lifetime

- This section is informative. + The following behaviors provide a normative description of the + conditions under which an AudioNode is alive, meaning that it MUST + be retained in the graph by an implementation. Where these + conditions do not apply, AudioNodes MAY be released by an + implementation. Additionally, implementations may apply other + methods to avoid unnecessary resource usage and unbounded memory + growth of unused/finished nodes.

- An implementation may choose any method to avoid unnecessary - resource usage and unbounded memory growth of unused/finished - nodes. The following is a description to help guide the general - expectation of how node lifetime would be managed. -

-

- An AudioNode will live as long as there are any - references to it. There are several types of references: + An AudioNode must remain alive as long as there + are any references to it. There are several types of references:

  1. A normal JavaScript reference obeying normal garbage From da51af0a9593377c03bf3a5013abe9e69fb0536a Mon Sep 17 00:00:00 2001 From: joeberkovitz Date: Tue, 7 Mar 2017 10:24:14 -0500 Subject: [PATCH 2/3] =?UTF-8?q?Remove=20sentence=20about=20=E2=80=9CAdditi?= =?UTF-8?q?onally,=20implementations=20may=20apply=20other=20methods?= =?UTF-8?q?=E2=80=A6=E2=80=9D=20which=20seems=20not=20to=20say=20anything?= =?UTF-8?q?=20useful.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- index.html | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/index.html b/index.html index 54b4a6ac5..018dc7579 100644 --- a/index.html +++ b/index.html @@ -3096,9 +3096,7 @@

    conditions under which an AudioNode is alive, meaning that it MUST be retained in the graph by an implementation. Where these conditions do not apply, AudioNodes MAY be released by an - implementation. Additionally, implementations may apply other - methods to avoid unnecessary resource usage and unbounded memory - growth of unused/finished nodes. + implementation.

    An AudioNode must remain alive as long as there From 285992469a97e2e6a603390fab1940a588632660 Mon Sep 17 00:00:00 2001 From: joeberkovitz Date: Mon, 27 Mar 2017 12:24:32 -0400 Subject: [PATCH 3/3] Incorporate @padenot feedback --- index.html | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index 018dc7579..6abdec7cf 100644 --- a/index.html +++ b/index.html @@ -3093,14 +3093,13 @@

    The following behaviors provide a normative description of the - conditions under which an AudioNode is alive, meaning that it MUST - be retained in the graph by an implementation. Where these - conditions do not apply, AudioNodes MAY be released by an + conditions under which an AudioNode is alive, meaning that + it MUST be retained in the graph by an implementation. Where these + conditions do not apply, AudioNodes MAY be released by an implementation.

    - An AudioNode must remain alive as long as there - are any references to it. There are several types of references: + There are several types of references:

    1. A normal JavaScript reference obeying normal garbage