{"id":1490,"date":"2011-11-16T16:10:36","date_gmt":"2011-11-16T05:10:36","guid":{"rendered":"http:\/\/blog.mozilla.org\/nnethercote\/?p=1490"},"modified":"2011-11-16T16:10:36","modified_gmt":"2011-11-16T05:10:36","slug":"memshrink-progress-report-week-22","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/nnethercote\/2011\/11\/16\/memshrink-progress-report-week-22\/","title":{"rendered":"MemShrink progress report, week 22"},"content":{"rendered":"

This was a quieter week.<\/p>\n

Andrew McCreight finished his static analysis to detect cycle collector leaks<\/a>.\u00a0 See the details in the bug (and talk to Andrew) if you are interested in using this analysis.<\/p>\n

I shrunk the size of js::HashTable<\/a> by 4 bytes on 32-bit platforms and 8 bytes on 64-bit platforms.\u00a0 This saves a few 10s or 100s of KB on typical workloads.<\/p>\n

Marco Bonardo decreased the default maximum page size of SQLite connections<\/a>, which can reduce SQLite memory usage somewhat.<\/p>\n

Olli Pettay avoided some wasted space in one of the cycle collector’s data structures<\/a>.\u00a0 The cycle collector uses lots of memory but for a short time when it runs;\u00a0 this change will reduce the size of this memory spike.<\/p>\n

Gian-Carlo Pascutto added a memory reporter for one of the data structures used by the url-classifier<\/a>.\u00a0 This shows up in about:memory under “explicit\/storage\/prefixset” and is often over 1MB.<\/p>\n

Justin Lebar improved the measurement of nsTArray’s memory usage<\/a>, which will reduce the size of “heap-unclassified” in about:memory by a small amount.<\/p>\n

Justin also wrote a good blog post about the challenges of addressing leaks in add-ons<\/a>.<\/p>\n

We only had seven new MemShrink bugs to triage in today’s meeting;\u00a0 I’m pretty sure that is the fewest we’ve ever had.\u00a0 Here are the current bug counts.<\/p>\n