Performance/MemShrink: Difference between revisions

Jump to navigation Jump to search
Line 212: Line 212:
Nonetheless, we've created a memory benchmark and are tracking Firefox's performance on it over time, to provide a sense of MemShrink progress and detect regressions.  It is available at http://areweslimyet.com/.
Nonetheless, we've created a memory benchmark and are tracking Firefox's performance on it over time, to provide a sense of MemShrink progress and detect regressions.  It is available at http://areweslimyet.com/.


== Current B2G memshrink priorities ==
== Current B2G MemShrink priorities ==


This is a list of the bugs we're currently looking at for B2G/MemShrink.
See the [https://etherpad.mozilla.org/e3fTHj5FV6 etherpad] for current B2G MemShrink priorities.
 
* {{bug|897684}} - Calling navigator.mozApps.mgmt.getAll() leaks the apps
* {{bug|898990}} - Long CC pauses in Leo's testing.  (All dependent issues fixed on trunk?)
* {{bug|899437}} - Zombie foreground process.  This is pretty bad.
Confirmed users
1,345

edits

Navigation menu