Summary: | [Chromium] fast/frames/meta-refresh-user-gesture.html is crashy on Windows. | ||
---|---|---|---|
Product: | WebKit | Reporter: | John Knottenbelt <jknotten> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | jnd, rniwa |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
John Knottenbelt
2011-07-21 08:35:59 PDT
Thanks for report John. If there is no collision, I will look at this today. *** Bug 64948 has been marked as a duplicate of this bug. *** cause by a race condition, a patch will be provided later. This bug was caused by different threads in DRT chromium port may try to initialize the standard_schemes global variable at same time. According to the InitStandardSchemes implementation in url_util.cc, when one thread was calling InitStandardSchemes, another thread might think the standard_schemes is completed, then called LowerCaseEqualsASCII to compare whether the specified scheme is one of standard schmemes, but standard_schemes->at(i) might return null pointer at this point (see method DoIsStandard in url_util.cc). There was a similar bug on http://code.google.com/p/google-url/issues/detail?id=17. The fix is pretty easy and provided in http://code.google.com/p/google-url/issues/detail?id=17. Which is to call standard_schemes initialization when initializing the program before other threads generate GURL object. From my understanding, we should call the URL library Initialization in webkit_support::SetUpTestEnvironment which is in Chromium source path. A fix may be submitted to Chromium, let's keep this bug open. Will close it when the CL landed in Chromium. chromium bug: http://code.google.com/p/chromium/issues/detail?id=90503 fix in chromium http://src.chromium.org/viewvc/chrome?view=rev&revision=94216 |