- From: Peter van der Noord <peterdunord@gmail.com>
- Date: Wed, 18 Jul 2012 00:08:30 +0200
- To: Chris Wilson <cwilso@google.com>
- Cc: Raymond Toy <rtoy@google.com>, public-audio@w3.org
Received on Tuesday, 17 July 2012 22:08:52 UTC
> I think it's changing something about the streaming from Peter's server What does "it" refer to in that sentence? 2012/7/17 Chris Wilson <cwilso@google.com> > I think it's changing something about the streaming from Peter's server > when it's being piped into the MediaElementSourceNode. I still repro the > crash, on Chrome 22. If I don't connect the MediaElementSourceNode, it > doesn't crash. > > > On Tue, Jul 17, 2012 at 1:59 PM, Raymond Toy <rtoy@google.com> wrote: > >> >> >> On Tue, Jul 17, 2012 at 1:38 PM, Peter van der Noord < >> peterdunord@gmail.com> wrote: >> >>> That is really, really weird...i can't think of anything that could do >>> that - my codes adds two modules and a connection. Without the analyser, >>> there's nothing going in the background. >>> >>> Is there a way that Chrome can tell more about that error (Failed to >>> load resource), as in a call stack? >>> >> >> Don't know if this will help or not, but you can bring up a javascript >> console. Shift+Ctrl+J (or use the wrench->Tools->JavascriptConsole. >> >> (And for the record, I cannot reproduce the issue on my machine with >> Chrome 22.) >> >> Ray >> >> >
Received on Tuesday, 17 July 2012 22:08:52 UTC