Till Schneidereit implemented sharing of bytecode and related script data<\/a>.\u00a0 This can result in significant savings, especially if you have multiple tabs open from the same site.\u00a0 For example, with 10 articles open from theage.com.au<\/a> I saw an 11.6 MiB saving.\u00a0 This was a MemShrink:P1, and its fix completes half of the “Better Script Handling” item from the MemShrink big ticket items list<\/a>.<\/p>\n Terrence Cole fixed a bad regression that was causing multi-GiB memory spikes when using certain regular expressions<\/a>.\u00a0 He landed this fix on the Nightly, Aurora and Beta channels.<\/p>\n I reduced<\/a> the overhead<\/a> of small compartments a little.\u00a0 This reduced the size of an unloaded tab<\/a> from 222 KiB to 192 KiB on 64-bit platforms.<\/p>\n Jason Orendorff removed some source notes<\/a> that are no longer required now that SpiderMonkey’s decompiler has been removed.\u00a0 This slightly reduces the size of the “script-data” entries in about:memory.<\/p>\n I modified js::Vector so that it doesn’t waste space when its elements have a size that is not a power of two<\/a>.<\/p>\n Chris Jones fixed a bad leak in the IPC code<\/a>.\u00a0 This is a big deal because B2G testing has found<\/a> several<\/a> cases<\/a> of steadily growing memory consumption that lead to the devices becoming unusable, and there’s a good chance that this leak was responsible for some of them.\u00a0 More testing is needed to determine exactly how many problems this has fixed.<\/p>\n It’s not surprising that IPC code is causing B2G problems, because that is code that desktop Firefox uses only lightly (for out-of-process plug-ins), whereas B2G uses it very heavily.\u00a0 There’s a bug open for detecting such leaks<\/a> that should be fairly easy to implement, and potentially could lead to big fixes, which is currently looking for an owner.<\/p>\n Timothy Nikkel reduced the memory consumed by Matthew Gregan fixed a bug, present only in Firefox 17 ESR, that was causing HTML5 videos to consume multiple GiBs of memory<\/a>.<\/p>\n Alexandre Poirot fixed another leak in the Add-on SDK<\/a>.<\/p>\n Jonathan Kew reduced the amount of memory consumed by textruns when Facebook Messenger is enabled<\/a>.<\/p>\nB2G<\/h3>\n
Miscellaneous<\/h3>\n
display:none<\/code> elements<\/a>.\u00a0 This was a tricky bug that was landed and then backed out multiple times due to subtle test failures.\u00a0 And while this bug has benefits of its own, it is most notable for the fact that it was blocking bug 689623<\/a>, which is the key bug that will help us start to fix Firefox’s problems with image-heavy pages.\u00a0 (And 689623 itself is close to landing now, with 13 r+’d patches.)<\/p>\n