Closed Bug 710927 Opened 13 years ago Closed 2 years ago

Track web page event/task costs in terms of cpu time

Categories

(Core :: DOM: Core & HTML, enhancement, P5)

Product:
Core
Component:
DOM: Core & HTML
Type:
enhancement

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: taras.mozilla, Unassigned)

References

Details

(Whiteboard: [Snappy:P2])

Would be great to be able to tag events as coming from a specific tab/chrome function/etc. This would help with tracking down browser lag.
is event.target not enough? you can get the principal/url from that.
(In reply to Olli Pettay [:smaug] from comment #1) > is event.target not enough? you can get the principal/url from that. Can you suggest a good way to tally cost of these events per target? Ie is there a logical place in the code that sees all events that we can hook into?
Do you really want to see all the events? If so, add something to nsEventDispatcher::Dispatch(). But if just some subset of common events, like mouse events etc is enough, you could perhaps add capturing event listeners to chrome.
(In reply to Olli Pettay [:smaug] from comment #3) > Do you really want to see all the events? If so, add something to > nsEventDispatcher::Dispatch(). > But if just some subset of common events, like mouse events etc is enough, > you could perhaps add > capturing event listeners to chrome. I'm mainly interested in non-interactive webpage events. I think that means setTimeouts and XHR handlers.
What has setTimeout to do with DOM Events?
Ok, so this is not about DOM events, but about cases where C++ ends up calling content JS, So, MutationObserver's microtasks ("the outermost script execution in the innermost task") could be useful here. Other thing to count is layout flushes.
Component: DOM: Events → DOM
QA Contact: events → general
Blocks: 711650
Summary: Add origin info to events → Track web page event/task costs in terms of cpu time
Blocks: 400120
Blocks: 712731
Whiteboard: [Snappy] → [Snappy:P2]
Hardware: x86 → All
OS: Windows 7 → All
Severity: normal → enhancement
Version: unspecified → Trunk
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: normal → S3

This is a rather vague idea filed more than a decade ago. If somebody has a concrete plan, a new bug is probably better.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.