[Webkit-unassigned] [Bug 51067] New: Assertion failure: element->inDocument() in AsyncScriptRunner::executeScriptSoon()

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=51067

           Summary: Assertion failure: element->inDocument() in
                    AsyncScriptRunner::executeScriptSoon()
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: NeedsRadar
          Severity: Normal
          Priority: P1
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ap at webkit.org
                CC: abarth at webkit.org, tonyg at chromium.org


Created an attachment (id=76587)
 --> (https://bugs.webkit.org/attachment.cgi?id=76587&action=review)
test case (will assert)

There is nothing that guarantees this. See attached test case.

I haven't checked what release mode consequences are.

In fact, looks like this test also shows another bug: we shouldn't be getting to executeScriptSoon() from error()!

#0    0x102e4c866 in WebCore::AsyncScriptRunner::executeScriptSoon at AsyncScriptRunner.cpp:57
#1    0x1038d1ccc in WebCore::ScriptElement::notifyFinished at ScriptElement.cpp:245
#2    0x102ea06aa in WebCore::CachedScript::checkNotify at CachedScript.cpp:100
#3    0x102ea072b in WebCore::CachedScript::error at CachedScript.cpp:108
#4    0x10367f62f in WebCore::Loader::didFail at loader.cpp:213
#5    0x10367f6c7 in WebCore::Loader::didFail at loader.cpp:190
#6    0x103957261 in WebCore::SubresourceLoader::didFail at SubresourceLoader.cpp:200
#7    0x10389cc07 in WebCore::ResourceLoader::didFail at ResourceLoader.cpp:444

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.