Re: Strange crashes when using media-element

No, I do not.  Even if I stream it from your server.

On Tue, Jul 17, 2012 at 3:46 PM, Peter van der Noord
<peterdunord@gmail.com>wrote:

> And just to be clear: you don't get the crash when creating an htmlfile
> yourself, with the same audiotag, and a couple of lines to add the 2 nodes
> and the connection?
>
> Could it be some kind of network/proxy/buffering/caching issue? (i'm no
> expert on these subjects) It's strange that i do get the crash at work, but
> not at home - with both exactly the same version of chrome.
>
> Peter
>
> Op 18 jul. 2012 om 00:33 heeft Chris Wilson <cwilso@google.com> het
> volgende geschreven:
>
> The last part of the sentence: "when it's being piped into MESN".
>  Refactored sentence:
>
> "Being piped into a MediaElementSourceNode [rather than left to play back
> as a normal <audio>] appears to be changing something about the way the
> content is streamed, and that's triggering the crash."
>
> On Tue, Jul 17, 2012 at 3:08 PM, Peter van der Noord <
> peterdunord@gmail.com> wrote:
>
>> >  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
>>>>
>>>>
>>>
>>
>