Bug 20852 - Nightly builds crash in new Dromaeo test
Summary: Nightly builds crash in new Dromaeo test
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL: http://dromaeo.com
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-15 02:20 PDT by wellofsouls
Modified: 2008-10-07 12:24 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description wellofsouls 2008-09-15 02:20:37 PDT 
all nightly builds crash in the newly updated Dromaeo test on Windows platforms.
Comment 1 Mark Rowe (bdash) 2008-09-15 12:40:20 PDT 
This is a dupe of an existing bug report.
Comment 2 wellofsouls 2008-09-15 18:55:17 PDT 
what existing bug is it? I've searched around but can't seem to find anything similar.

BTW, it always crashes at the DOM Attributes (Prototype) subtest.
Comment 3 Mark Rowe (bdash) 2008-09-16 10:07:30 PDT 
Please try with the r36446 nightly build.
Comment 4 Mark Rowe (bdash) 2008-09-16 10:08:15 PDT 
The other bug that I was thinking of was bug 20703.
Comment 5 wellofsouls 2008-09-16 22:41:28 PDT 
(In reply to comment #3)
> Please try with the r36446 nightly build.
> 

thanks, r36446 no longer crashes in the test, however it seems many subtests fail with 0ms results.

http://dromaeo.com/?id=42065
Comment 6 André Braga 2008-10-07 11:27:50 PDT 
Crashes are back for some revisions now, r37076 inclusive. Leopard 10.5.5 Intel. Both on the nightlies and on self-compiled, Xcode 3.1.1-2517, doesn't matter if I set GCC_VERSION to 4.0 or 4.2.

Didn't happen on r37300. Sorry I can't bisect, the laptop almost melts when I compile WebKit :)

Stack crawl coming.
Comment 7 Mark Rowe (bdash) 2008-10-07 11:34:17 PDT 
Moving back to resolved.  If you're seeing a crash, please file a new bug report.
Comment 8 André Braga 2008-10-07 12:24:51 PDT 
Er, I obviously meant r37376 on the last message.

Rolling out r37370 fixed it.

Thanks!