Closed Bug 550242 Opened 14 years ago Closed 7 years ago

Need a runtime extension bad-practice checker

Categories

(DevTools :: General, defect, P4)

Product:
DevTools
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: taras.mozilla, Unassigned)

References

Details

(Whiteboard: [ts][snappy:p2]) 

During startup work we've identified a number of bad practices that kill startup performance. We should make a tool that logs bad behaviors and presents them in a report-like fashion.
Example things to look for:
a) How much filesystem-activity (open/stat) calls can be attributed to a particular extension/module/component?
b) Does the extension do a lot of if (exists(file)) open(file)
c) Are there an overuse of slow xpconnect calls, excessive ui updates, etc.

These aren't trivial things to diagnose, but should be doable and very helpful for keeping firefox efficient.
Whiteboard: [ts]
OS: Linux → All
Hardware: x86 → All
Depends on: 558200
Sounds like this would be good to implement in the console.
actually, scratch that (comment #1) –– this probably should be something turned on by a pref that would report to stdio.
filter on PEGASUS
Priority: -- → P4
Whiteboard: [ts] → [ts][snappy]
Todo: list 3 usecases for this.
Whiteboard: [ts][snappy] → [ts][snappy:p2]
Inactive for 6 years. Closing now.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.