Summary: | CrashTracer: WebProcess at com.apple.WebCore: WebCore::toScriptElementIfPossible + 4 | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Antti Koivisto <koivisto> | ||||
Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | cdumez, commit-queue, ddkilzer, esprehn+autocc, gavinp, kangil.han, lquinn | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Antti Koivisto
2015-04-22 10:32:10 PDT
Created attachment 251342 [details]
patch
Comment on attachment 251342 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=251342&action=review r=me as it seems safe but we should revisit this later on. > Source/WebCore/ChangeLog:5 > + Would be nice to have the radar here as well. > Source/WebCore/ChangeLog:19 > + in ScriptRunner::notifyScriptReady fails to find scriptElement and we are left with null entry in s/in/If In builds without the fix, I can reproduce this crash reliably by visiting http://www.hifi-forum.de/viewthread-152-4332.html (using the BlackBerry port or EFL port). (In reply to comment #5) > In builds without the fix, I can reproduce this crash reliably by visiting > http://www.hifi-forum.de/viewthread-152-4332.html (using the BlackBerry port > or EFL port). I have just tried visiting this URL with WebKit ToT / Mac port and it did not crash. (In reply to comment #5) > In builds without the fix, I can reproduce this crash reliably by visiting > http://www.hifi-forum.de/viewthread-152-4332.html (using the BlackBerry port > or EFL port). I can't repro it either. Could you try debugging it? Just reproing the crash on debug build might give a backtrace explaining how this becomes null. Unfortunately, it's no longer reproducing for me today. |