Bug #207
Large Memory Leak with Firefox 3.0b5
| Status: | Closed | Start: | ||
| Priority: | High | Due date: | ||
| Assigned to: | Andrew Dolgov | % Done: | 0% |
|
| Category: | interface | |||
| Target version: | - | |||
| Resolution: | worksforme |
Description
I Have been using TT-RSS for a couple of months now. RSS feeds have accumulated several articles.
I am finding that when ever TT-RSS is retrieving the list of articles for a feed, Firefox memory usage skyrockets (up to 800MB) and does not go down.
This seems to occur after Firefox has downloaded the list of articles from the server and begins to populate the list. It makes the browser hang for about 2-3 seconds depending on the power of the CPU and takes up a lot of RAM. During the period Firefox is locked up RAM increases very fast from 60MB to at least 500MB.
This lock up in Firefox can occasionally cause it to crash.
History
Updated by Andrew Dolgov 808 days ago
As far as I understand, Javascript has garbage collection, so you can't really leak memory with it unless the interpreter is broken. If Mozilla interpreter leaks, it should be taken to Mozilla devs. Good luck with that...
Anyway, I don't see anything like that with FF3b5. Do you have any extensions installed? Try with blank profile, I remember that helping some people.
Updated by trac-user - 462 days ago
I've had this problem with every version of Firefox 3.0, to the extent I had to stop using tt-rss.
I missed it, forgot why I stopped using it and came back and within 5mins it started again. I have a long list of feeds, around 40-50 and it also occurs when updating.
The memory leak becomes so large, it pages it then HDD usage also becomes 100% thereby rendering the system unusable. Closing the Firefox tab that tt-rss is on and within 20-30sec the system comes good again.
Anything I can provide that will help debug it, please let me know.
Updated by trac-user - 462 days ago
Same user from 04/24/09 05:56:36 (downforce).
Just tried installing Google Chrome instead and exactly same behaviour. 1.6GB physical RAM (out of 2GB total) and 1.7GB page file.
Can't just be a Mozilla issue.
Updated by Andrew Dolgov 462 days ago
This has been running for a week or so:
http://bah.org.ru/images/shots/2009-04-24_ff_mem_usage.png
Should be self-explanatory.
How many articles are you trying to load? If your article limit value is set to All, try setting it to something sensible.
Updated by Andrew Dolgov 146 days ago
- Status changed from New to Closed
- Resolution set to worksforme