Bug 79106

Summary: Web Inspector: timeline hangs on a page with deep chain of nested events.
Product: WebKit Reporter: Yury Semikhatsky <yurys>
Component: Web Inspector (Deprecated)Assignee: Yury Semikhatsky <yurys>
Status: RESOLVED FIXED    
Severity: Normal CC: apavlov, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, rik, timothy, yurys
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Test page
none
Patch pfeldman: review+

Yury Semikhatsky
Reported 2012-02-21 07:04:40 PST
Created attachment 127963 [details] Test page Try to run timeline on the attached page. Result: After awhile Timeline will hang. Stack overflow exception in the front-end.
Attachments
Test page (122 bytes, text/html)
2012-02-21 07:04 PST, Yury Semikhatsky
no flags
Patch (5.42 KB, patch)
2012-02-21 07:08 PST, Yury Semikhatsky
pfeldman: review+
Yury Semikhatsky
Comment 1 2012-02-21 07:08:21 PST
Yury Semikhatsky
Comment 2 2012-02-21 08:14:11 PST
Timothy Hatcher
Comment 3 2012-02-24 10:40:33 PST
How are timers nesting anyway? I thought they had to return to the run loop before firing the next timer. I think the fact that the timeline nests them should be considered a bug.
Pavel Feldman
Comment 4 2012-02-24 10:50:42 PST
(In reply to comment #3) > How are timers nesting anyway? I thought they had to return to the run loop before firing the next timer. I think the fact that the timeline nests them should be considered a bug. There is a timeline mode (turned on by default) that binds asynchronous events to their causes. As a result, Timer Fire falls to under the Set Timeout. In case animation is implemented as a series of such events, they all form a giant connected branch. It draws us out of stack bounds. There is now a way to disable this binding.
Note You need to log in before you can comment on or make changes to this bug.