(This is from a commenter named "mindugo" on my blog: http://blog.mozilla.org/nnethercote/2012/09/05/memshrink-progress-week-63-64/comment-page-1/#comment-7439. I haven't tried to reproduce it.) I think LastPass extension is still leaking to heap-unclassified and it’s very similar to “Restartless Restart + SmartSearch” leak. I tested like this: 1. Install latest Nightly build. 2. Create new profile. 3. Install “LastPass” (https://addons.mozilla.org/en-US/firefox/addon/lastpass-password-manager). 4. Install “Restartless Restart 8″ (https://addons.mozilla.org/en-US/firefox/addon/restartless-restart). 5. Restart Firefox. 6. Login to LastPass account using extension. 7. Open a new tab with about:memory. Heap-unclassified is ~ 7-8Mb. 8. Open a new tab with http://www.gsmarena.com/apple_ipad_3-review-739.php 9. Click on the first iPad image in the review – a popup opens. 10. Close the popup. 11. Repeat 9-10 steps 20 times. 12. Go to about:memory tab and click “Minimize memory usage” button. 13. Check line with heap-unclassified – it is ~75Mb and never goes down. This doesn’t happen (heap-unclassified stays at about the same level with just minimal increase) while user IS NOT logged-in to LastPass account, even if LastPass extention is installed and enabled in Firefox. I reported this to LastPass support team a while ago and they could reproduce the problem eventually. You can get similar result with LastPass and some other extensions installed, e.g. TabGroups Menu.
I can confirm this. With LastPass insalled, heap-unclassified seems to grow fairly rapidly and consistently as websites are visited. This does not happen without the add-on installed.
Whiteboard: [MemShrink] → [MemShrink:P2]
Is this resolved yet? I was looking into why my Firefox memory seems to be growing and this is one of those addons I really need so it was the only one I haven't disabled when trying to find memory leaks. It seems like this is the culprit for sure of my Firefox going from 400mB to 1400mB over the course of 24 hours.
This doesn't seem to be an issue anymore.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.