Changeset 92239 in webkit
- Timestamp:
- Aug 2, 2011 3:17:51 PM (13 years ago)
- Location:
- trunk/Source/WebCore
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebCore/ChangeLog
r92238 r92239 1 2011-08-02 Gavin Peters <gavinp@chromium.org> 2 3 fail earlier to track down null CachedScript execution 4 https://bugs.webkit.org/show_bug.cgi?id=65563 5 6 Over in http://code.google.com/p/chromium/issues/detail?id=75604 I can't reproduce the problem. Careful reading of the code hasn't led me 7 to an obvious cause either. This patch should cause failure earlier, and lead to better stacks. I'll watch Chrome Canary's crash 8 uploads carefully, and remove this CRASH() (and fix the underlying problem) once I understand it. 9 10 Reviewed by Alexey Proskuryakov. 11 12 No new tests, as my goal here is to get telemetry on a bug that I cannot reproduce. 13 14 * dom/ScriptRunner.cpp: 15 (WebCore::ScriptRunner::queueScriptForExecution): 16 1 17 2011-08-02 Sailesh Agrawal <sail@chromium.org> 2 18 -
trunk/Source/WebCore/dom/ScriptRunner.cpp
r81198 r92239 53 53 { 54 54 ASSERT(scriptElement); 55 56 // Temporary: intended to help debug how null CachedScript objects can even get queued for execution, which 57 // seems to sometimes happen (see http://code.google.com/p/chromium/issues/detail?id=75604 ) 58 if (!cachedScript.get()) 59 CRASH(); 55 60 56 61 Element* element = scriptElement->element();
Note: See TracChangeset
for help on using the changeset viewer.