Bug 101297 - On Apple Windows port, running DRT locally crashes after r128583 and related changes
Summary: On Apple Windows port, running DRT locally crashes after r128583 and related ...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-05 20:11 PST by Roger Fong
Modified: 2012-11-28 11:42 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Fong 2012-11-05 20:11:46 PST
The crash resolves in hash table code. 
When DRT calls WebKitCreateInstance it tries to populate a hash table. At some point it needs to expand the table and reinsert objects into the new larger table but for some reason one of the objects it tries to reinsert has been marked as deleted and things go downhill from there.

This problem only reproduces locally on my Windows machine. The Apple Windows port test bots don't seem to have the same issue.

Originally, there were crashes occuring after r128583. These were fixed later by a workaround and then an actual fix in r128850.

I failed to notice this fix while I was bisecting but I believe that the crashing form r128583 and the ones occuring now are because of different reasons. Most likely soething after r 128850 made things crash again.

I'm going to investigate r128850 to see whether or not the crashes still occur at that revision.
Comment 1 Roger Fong 2012-11-06 01:27:39 PST
It crashes on r128850 as well. 
In addition. I tried running the tests locally on the bots. It also crashes there an generates an error ::LoadLibraryW failed (whatever that means).

Anyways, this means that it is not a problem specific to my setup but simply running tests locally in general.

I may just have to rely on webkit test runner but this is definitely an issue we need to solve.

I'll run DRT from VS2005 and print out the crashing stack trace. I doubt it will be particularly helpful though.
Comment 2 Kent Tamura 2012-11-06 01:41:54 PST
What about running r128582 or older locally?
Comment 3 Roger Fong 2012-11-06 10:37:43 PST
everything runs fine before r128583, i'm now running it on r128629, the workaround patch
Comment 4 Roger Fong 2012-11-06 11:19:43 PST
o hey, it doesn't crash there...there's a decent chance that the crash actually has nothing to do at all with the revisions I mentioned earlier. I'll keep regression testing.