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.
10 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.)
6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.