Closed
Bug 491350
Opened 15 years ago
Closed 11 years ago
Time and profile out-of-main-event-loop latency
Categories
(Developer Infrastructure :: Source Code Analysis, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: cjones, Unassigned)
References
Details
We want to do the following (1) Firefox receives an X event (2) The instrumentation tool starts profiling executing code until FF returns to the event loop (3) Stop profiling, and perhaps if the time lag between the event and processing the event is too high (>100 ms?), save the sample. There are numerous ways to implement such a tool.
Comment 1•15 years ago
|
||
See also: http://shaver.off.net/diary/2007/08/25/tbeachball/ (I thought that made it into a bug, but I can't find it.)
Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Core → Firefox Build System
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•