Summary: | Assertion hit: ASSERT(!m_parserScheduler) in ~HTMLDocumentParser() | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Chris Dumez <cdumez> | ||||
Component: | DOM | Assignee: | Chris Dumez <cdumez> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, cdumez, commit-queue, darin, ddkilzer, esprehn+autocc, kangil.han, rniwa, ryanhaddad, sam, webkit-bug-importer | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Chris Dumez
2016-08-23 08:58:36 PDT
In Document::implicitOpen(), we call in this order: 1. cancelParsing(); // Clears out m_parser 2. removeChildren(); // May cause JS execution and therefore re-populate m_parser 3. m_parser = createParser(); // Expects m_parser to be null. Looking at the spec: https://html.spec.whatwg.org/#dom-document-open It says: Remove all child nodes of the document, without firing any mutation events. (step 15) So we should probably not fire mutation events. Created attachment 286886 [details]
Patch
Comment on attachment 286886 [details] Patch Clearing flags on attachment: 286886 Committed r204936: <http://trac.webkit.org/changeset/204936> All reviewed patches have been landed. Closing bug. |