[webkit-dev] Crashing Workers Code?

Eric Seidel eric at webkit.org
Mon Mar 29 18:10:19 PDT 2010


>From my experience watching the bots, I would say the Qt build is
relatively stable, so I suspect it's just good at reproducing this
crasher.

The Qt build is nice that it produces stack traces for every crash.
Sadly their useless until
https://bugs.webkit.org/show_bug.cgi?id=33654 is fixed.

On Mon, Mar 29, 2010 at 5:47 PM, Drew Wilson <atwilson at google.com> wrote:
> I'll also note that a disproportionate number of those bugs are happening on
> the Qt build. This either means that the Qt build is awesome at reproducing
> this race condition, or that there's some other flakiness on that build that
> is exposed with workers.
> -atw
>
> On Mon, Mar 29, 2010 at 5:26 PM, Darin Adler <darin at apple.com> wrote:
>>
>> On Mar 29, 2010, at 5:14 PM, Dmitry Titov wrote:
>>
>> > JSC workers are terminated by setting a 1-ms timeout. V8 workers
>> > terminate by throwing exception of a special kind and then checking for it
>> > in C++ code.
>>
>> There is precedent in JavaScriptCore for using a special exception to
>> terminate code. InterruptedExecutionError is used for this purpose. I could
>> imagine having something similar for workers. A timeout sounds like a poor
>> way to do it.
>>
>>    -- Darin
>>
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>


More information about the webkit-dev mailing list