Bug 129817

Summary: DomTree.requestContentFlowList fails sometimes when reloading page
Product: WebKit Reporter: Blaze Burg <bburg>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: achicu, betravis, graouts, joepeck, timothy, webkit-bug-importer, WebkitBugTracker
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Blaze Burg
Reported 2014-03-06 12:55:18 PST
This is a mostly benign error: `Error while getting the named flows for document 35: Could not find node with given id` that happens when reloading a page. It seems that the frontend and backend are racing, or that the frontend is using a document id that becomes stale by the time the request reaches the backend. It seems that this code should go through DOMTree.requestDocument so it always gets the correct document id, but upon inspecting the protocol traffic it seems to request content flow list immediately before requesting the document. This failure is newly exposed by converting inspector model tests (tracked by https://webkit.org/b/129217) so the patch in that bug will mark the following tests as flaky: inspector/dom/content-flow-list.html inspector/dom/content-flow-content-removal.html
Attachments
Joseph Pecoraro
Comment 1 2015-07-31 18:15:28 PDT
I don't see this anymore. Closing.
Note You need to log in before you can comment on or make changes to this bug.