They did both. The leak was in numereous add-ons code, but they were able to cha...

lillycat on May 8, 2012 | parent | context | favorite | on: Firefox finally plugs the leak

They did both. The leak was in numereous add-ons code, but they were able to change the semantics of the API to remove all these leaks. But that breaks things in some edge cases, but that was deemed acceptable (one time fix in some extensions, mainly those using Jetpack needing to embed the latest versions).

khuey on May 8, 2012 [–]

Actually it's looking like most of the breakage can be avoided by a simple change on our side.