Closed Bug 651580 Opened 14 years ago Closed 12 years ago

Identify code causing delays in the browser UI

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: dietrich, Unassigned)

References

Details

Now that bug 601268 has landed, we can start to look into ways of correlating event loop return lag with specific code. Two different approaches we've talked about taking when code takes too long to return to the main event loop: 1. Hooking into Shark (or other profiler). Great for Firefox developers familiar with low-level platform APIs. 2. Dumping the JS stack via the function callback hooks (bug 507012). Useful Firefox front-end devs, and add-on and web-devs. Provides easy correlation of JS code with responsiveness problems, possible with both chrome and content.
Depends on: 653701, 653703
OS: Mac OS X → All
Hardware: x86 → All
Making this depend on the new profiler, which obsoletes the earlier work done in these dependent bugs.
Depends on: 713227
No longer depends on: 653701, 653703
With SPS in place, I think this bug is done.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.