User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150513174244 Steps to reproduce: Go to either of these URLs: http://www.sfgate.com/ http://www.rolandgarros.com/en_FR/draws/index.html Monitor memory with about:memory or Windows Task Manager Actual results: Memory grows constantly -- even after gc, cc, and minimize memory. Eventually, Windows warn to close firefox because system is running out of memory. Google Chrome does not have problem with the same URLs. Expected results: Memory use should be constant like with Google Chrome.
Unable to replicate it for: UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 BuildId: 20150513174244 Version: 38.0.1 Nightly: UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:41.0) Gecko/20100101 Firefox/41.0 BuildID: 20150527030204 Version: 41.0a1
3 years ago
Component: Untriaged → DOM
Product: Firefox → Core
Does this happen in safe mode? In a clean profile?
Using (virgin) guest profile, I do not see the severe memory growth at sfgate.com. Memory does still grow (and shrinks a little) according to Windows Task Manager. So memory behavior is more tolerable. But, when I selected Show All Bookmarks, more severe memory growth started. So this appears to be caused by the bookmarks.
So you can reproduce ShowAllBookmarks causing some leak? Doesn't about:memory hint where the memory is consumed?
Yes, a saved report from about:memory would be useful here.
Let's close this for now, k1devnull if you're concerned about this still happening please feel free to reopen.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.