The test sends a message to the worker to close and also to reply with a message. Immediately, it sets up a timer for 500ms which will terminate the test. On slow machines, the timer may terminate test before the reply comes from the worker, so the actual dump is one message short. Fix is to start timer after the message comes. Patch coming.
Created attachment 53877 [details] Patch.
Comment on attachment 53877 [details] Patch. Ok. I'm sad that we have to setTimeout at all...
Landed: http://trac.webkit.org/changeset/57916
http://trac.webkit.org/changeset/57919 might have broken SnowLeopard Intel Release (Tests)
http://trac.webkit.org/changeset/57916 might have broken Qt Windows 32-bit Debug The following changes are on the blame list: http://trac.webkit.org/changeset/57909 http://trac.webkit.org/changeset/57910 http://trac.webkit.org/changeset/57911 http://trac.webkit.org/changeset/57913 http://trac.webkit.org/changeset/57914 http://trac.webkit.org/changeset/57915 http://trac.webkit.org/changeset/57916 http://trac.webkit.org/changeset/57917 http://trac.webkit.org/changeset/57918