W3C home > Mailing lists > Public > public-audio-dev@w3.org > September 2016

Re: Web Audio Crashes in Chrome 52+

From: Raymond Toy <rtoy@google.com>
Date: Tue, 6 Sep 2016 09:13:16 -0700
Message-ID: <CAE3TgXGviEYFssQu=6KZ6-1T51n8gS3RUo4QPyK_CMtB0oZtHA@mail.gmail.com>
To: David Joy <david@noteflight.com>
Cc: "public-audio-dev@w3.org" <public-audio-dev@w3.org>
This isn't really the right place to file issues with browsers'
implementations of webaudio.  Since you're experiencing crashes with
Chrome, please file a bug at crbug.com/new and make sure to add
Blink->WebAudio as the component.  A repro case would certainly help too!

On Wed, Aug 31, 2016 at 1:16 PM, David Joy <david@noteflight.com> wrote:

> To any Chrome developers listening on this list:
>
> Noteflight is a Web Audio-heavy application, and since the release of
> Chrome 52, we've been experiencing a sharp increase in the volume of crash
> reports ("Aw, Snap" page) from our Noteflight users. Chrome 53 appears to
> exhibit the same problems; Canary (55) may be better, although it's
> difficult to be sure.
>
> We are wondering if you are aware of any instabilities introduced in
> Chrome 52 to Web Audio applications, and whether any workarounds or fixes
> are available in the near term. We've filed a crash report in the Chromium
> bugbase (642056) that may implicate audio as an ingredient in the crashes,
> although it's hard to be sure.
>
> Best, and thanks,
>
> -David Joy
> --
> David Joy
> Software Architect
> Noteflight LLC
>
> +1 617 909 4175
>
> 49R Day Street
> Somerville MA 02144
> USA
>
> "Bring music to life"
> www.noteflight.com
>
Received on Tuesday, 6 September 2016 16:13:59 UTC

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