[Webkit-unassigned] [Bug 89692] Web Inspector: show worker started and finished on timeline

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 27 13:18:58 PDT 2012


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





--- Comment #32 from Pavel Feldman <pfeldman at chromium.org>  2012-07-27 13:19:00 PST ---
> Even though the worker's javascript is processed on a separate thread it is still useful to know when a worker is created/terminated.  This is especially important on devices with limited system resources.  This is meant to be a surface level overview and for further details about how things run Web Workers can be inspected in their own timeline.

There are multiple timeline operation modes we are providing:

1. Performance angle. Workers should not be a big deal here. They operate elsewhere, while worker script loading is reflected in the page's timeline
2. Async causation analysis - we glue setTimeout with timer fire events in that mode. Also does not make much sense to the workers
3. Memory view (no correlation)
4. Frame mode (no correlation)
5. Getting to know what the program is doing when one has no clue

Workers fall to under (5), but many, many other things do too. I don't think we should add workers before we add most of the events there. That's why I am a bit reluctant to this change.

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



More information about the webkit-unassigned mailing list