Confirmed users
839
edits
Performance/MemShrink/Ideas: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "This is a list of ideas for improving the memory utilization in Firefox. This list originated at Sfink/Memory_Ideas. == Problem A: System too unusable to diagnose == When a...") |
No edit summary |
||
| Line 7: | Line 7: | ||
=== Solutions: Make it easier to get information out when the system is suffering === | === Solutions: Make it easier to get information out when the system is suffering === | ||
[[#A1]] Periodically log memory-related information (existing bug, I think? also | [[#A1]] Periodically log memory-related information (existing bug, I think? {{bug|662814}}? also | ||
telemetry) | telemetry) | ||
| Line 23: | Line 23: | ||
deactivate them too. | deactivate them too. | ||
[[#A6]] Early warning when memory usage is getting too high | [[#A6]] Early warning when memory usage is getting too high -- based on jlebar's work on memory pressure? | ||
[[#A7]] Crash reporter-like UI for reporting memory problems (do not require an | [[#A7]] Crash reporter-like UI for reporting memory problems (do not require an | ||
| Line 34: | Line 34: | ||
(all solutions from problem A are relevant here) | (all solutions from problem A are relevant here) | ||
[[#B1]] Provide a way to dump and submit a reachability graph | [[#B1]] Provide a way to dump and submit a reachability graph -- graph size could be a problem here, at least if done at a large scale? | ||
[[#B2]] Documentation for how to best help with a memory problem, with various | [[#B2]] Documentation for how to best help with a memory problem, with various | ||
steps to follow. | steps to follow. | ||
[[#B3]] Track memory to individual page/tab/compartment/principals. | [[#B3]] Track memory to individual page/tab/compartment/principals. -- this is done to some extent with per-compartment JS memory reporters. | ||
[[#B4]] Tools for generating profiles with subsets of addons installed (or for | [[#B4]] Tools for generating profiles with subsets of addons installed (or for | ||
| Line 46: | Line 46: | ||
[[#B5]] Tools for blaming memory usage on addons (eg detecting "safe" addons to | [[#B5]] Tools for blaming memory usage on addons (eg detecting "safe" addons to | ||
remove from consideration. Cross-referencing other users' addons and memory | remove from consideration. Cross-referencing other users' addons and memory | ||
usage similar to the crash correlation reports -- requires telemetry.) | usage similar to the crash correlation reports -- requires telemetry.) -- {{bug|671352}} is related. | ||
== Problem C: Knowledgeable users can't generate useful reports == | == Problem C: Knowledgeable users can't generate useful reports == | ||
| Line 55: | Line 55: | ||
The above problem B crossed into this, so everything there is relevant. | The above problem B crossed into this, so everything there is relevant. | ||
[[#C1]] Rationalize and document all of our various leak-detection tools. | [[#C1]] Rationalize and document all of our various leak-detection tools. -- bits and pieces on various wiki pages, but no good whole story page exists, afaik. | ||
[[#C2]] Automation and Windows equivalents of my /proc/<pid>/maps hacks | [[#C2]] Automation and Windows equivalents of my /proc/<pid>/maps hacks | ||