Closed
Bug 550242
Opened 15 years ago
Closed 7 years ago
Need a runtime extension bad-practice checker
Categories
(DevTools :: General, defect, P4)
DevTools
General
Tracking
(Not tracked)
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.
|
Reporter | |
Updated•15 years ago
|
Whiteboard: [ts]
|
||
Updated•15 years ago
|
OS: Linux → All
Hardware: x86 → All
|
||
Comment 1•14 years ago
|
||
Sounds like this would be good to implement in the console.
|
|
||
Comment 2•14 years ago
|
||
actually, scratch that (comment #1) –– this probably should be something turned on by a pref that would report to stdio.
|
|
Reporter | |
Updated•13 years ago
|
Whiteboard: [ts] → [ts][snappy]
|
|
Reporter | |
Comment 4•13 years ago
|
||
Todo: list 3 usecases for this.
Whiteboard: [ts][snappy] → [ts][snappy:p2]
|
||
Comment 5•7 years ago
|
||
Inactive for 6 years. Closing now.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
|
||
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•