Agreed, we (worker folks) should go investigate this further - it sounds like we may be getting lucky and we have a platform that can repro the crash more frequently.<div><br></div><div>I just wanted to mention that the main thing in the system that exercises the platform-specific thread/locking infrastructure is workers. If there are any synchronization bugs on a platform (or in a specific part of WebKit) they'll primarily show up as failures in Worker tests. I don't think that's what is happening here, but it's something to keep in mind.</div>
<div><br></div><div>-atw<br><br><div class="gmail_quote">On Mon, Mar 29, 2010 at 6:10 PM, Eric Seidel <span dir="ltr"><<a href="mailto:eric@webkit.org">eric@webkit.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
>From my experience watching the bots, I would say the Qt build is<br>
relatively stable, so I suspect it's just good at reproducing this<br>
crasher.<br>
<br>
The Qt build is nice that it produces stack traces for every crash.<br>
Sadly their useless until<br>
<a href="https://bugs.webkit.org/show_bug.cgi?id=33654" target="_blank">https://bugs.webkit.org/show_bug.cgi?id=33654</a> is fixed.<br>
<div><div></div><div class="h5"><br>
On Mon, Mar 29, 2010 at 5:47 PM, Drew Wilson <<a href="mailto:atwilson@google.com">atwilson@google.com</a>> wrote:<br>
> I'll also note that a disproportionate number of those bugs are happening on<br>
> the Qt build. This either means that the Qt build is awesome at reproducing<br>
> this race condition, or that there's some other flakiness on that build that<br>
> is exposed with workers.<br>
> -atw<br>
><br>
> On Mon, Mar 29, 2010 at 5:26 PM, Darin Adler <<a href="mailto:darin@apple.com">darin@apple.com</a>> wrote:<br>
>><br>
>> On Mar 29, 2010, at 5:14 PM, Dmitry Titov wrote:<br>
>><br>
>> > JSC workers are terminated by setting a 1-ms timeout. V8 workers<br>
>> > terminate by throwing exception of a special kind and then checking for it<br>
>> > in C++ code.<br>
>><br>
>> There is precedent in JavaScriptCore for using a special exception to<br>
>> terminate code. InterruptedExecutionError is used for this purpose. I could<br>
>> imagine having something similar for workers. A timeout sounds like a poor<br>
>> way to do it.<br>
>><br>
>> -- Darin<br>
>><br>
>> _______________________________________________<br>
>> webkit-dev mailing list<br>
>> <a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
>> <a href="http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev" target="_blank">http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> webkit-dev mailing list<br>
> <a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
> <a href="http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev" target="_blank">http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev</a><br>
><br>
><br>
</div></div></blockquote></div><br></div>