Changes

Jump to: navigation, search

Performance/MemShrink

1,058 bytes removed, 06:08, 25 July 2011
Tracking Current Leaks
* [[Performance/MemShrink/Meetings/2011-07-19|2011-07-19 minutes]]; [http://blog.mozilla.com/nnethercote/2011/07/20/memshrink-progress-week-5/ Week 5 report]
== Bug Tracking Current Leaks ==
We get lots Bugs tracked by the MemShrink project are prioritized by adding one of leak reports. Many of them are vague. It can be hard to tell when duplicates happen. They often aren't closed. This means that tracking them at a coarse granularity (eg. the "mlkMemShrink:P1", "MemShrink:P2" and or "footprintMemShrink:P3" keywords) ends up being of little use. So it's worthwhile tracking them on a per-release basisto the whiteboard.
* {{bug|659855}} is for leaks and quasi[https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=regexp&query_format=advanced&list_id=577353&status_whiteboard=MemShrink%5b%5e%3A%5d&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---leaks reported against Firefox 4 betas&resolution=DUPLICATE Unprioritized MemShrink bugs]. These are triaged regularly in meetings.* {{bug|659856}} is for leaks and quasi[https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---leaks reported against Firefox 4&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP1&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P1 bugs]. These are discussed regularly in meetings.* {{bug|659857}} [https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP2&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P2 bugs]. These are discussed occasionally in meetings. P2 is for leaks and quasi-leaks reported against Firefox 5the default priority.* {{bug|659858}} is for leaks and quasi[https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---leaks reported against Firefox 6&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP3&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P3 bugs]. These are discussed rarely in meetings.* {{bug|659856}} is for leaks and quasi[https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=--leaks reported against Firefox 7* {{bug|669241}} is for leaks and quasi-leaks reported against Firefox 8&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id All MemShrink bugs].
The following bugs are on There's also a longer timescale, because they track fewer bugs than the leak tracker bugs: * {{bug|640457}} for other memory use reductions in Firefox 5 and later versions* {{bug|640791}} for improvements to memory profiling in Firefox 5 and later versions All the above bugs are also prioritized by adding one of "MemShrink:P1", "MemShrink:P2" or "MemShrink:P3" to the whiteboard. * [https://bugzilla.mozilla.org/buglistshow_bug.cgi?list_idid=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP1&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P1 bugs]* [https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP2&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P2 bugs640791 tracking bug]* [https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP3&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P3 bugs]* [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=regexp&query_format=advanced&list_id=577353&status_whiteboard=MemShrink%5b%5e%3A%5d&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---&resolution=DUPLICATE Unprioritized MemShrink bugs]* [https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id All MemShrink bugs] The meaning of the priorities for leaks is as follows: * P1: For bugs that affect lots of users (or seriously hamper our ability relating to identify profiling, tools and isolate bugs)infrastructure.* P2: The default priority; used for (These bugs that aren't clearly overlap the P1 or , P2 and P3bug lists.* P3: For bugs that affect small number of users, eg. because the leak only manifests if multiple add-ons are installed. These priorities will be used to guide discussion in MemShrink meetings.)
== Goals ==
Confirm
1,345
edits

Navigation menu