Chrome memory leak issues on Firefox 3

RESOLVED INCOMPLETE

Status

()

Firefox
General
RESOLVED INCOMPLETE
9 years ago
7 years ago

People

(Reporter: Tarik Ansari, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-12-01], URL)

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.3.154.9 Safari/525.19
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

I am working on the development of a web application that intensively use JavaScript. We mainly use jQuery (with livequery), customized ExtJS features and custom classes.

We certainly still have a few pseudo-memory leaks issues (objects that could be cleared during execution, or memory that grow up when using a web page), but I am more concerned by what I think are real chrome memory leak issues that remain in Firefox 3 (high memory usage after closing all tabs).

Reproducible: Sometimes

Steps to Reproduce:
1. create an account at http://itemize-dev2.kei.com:3002/
2. make some items
3. toggle between list view/grid view, change pages etc
4. open other tabs of the application and do other actions
5. memory usage at this point should  be around 300MB-1.5GB
6. close tabs
7. memory usage is still very high, and the browser being using virtual memory, the application gets slow, Firefox need to be restarted



I have done testing using Leak Monitor, and it will a report of multiple memory leaks after closing a window coming from the following places:
- http://itemize-dev2.kei.com:3002/lib/nicEdit/nicEdit.js?1225149103, 237-237
- http://itemize-dev2.kei.com:3002/javascripts/ext-2.2-custom.js?1221849595, 10-1
- http://itemize-dev2.kei.com:3002/, 62-65
- http://itemize-dev2.kei.com:3002/lib/nicEdit/nicEdit.js?1225149103, 240-242
- http://itemize-dev2.kei.com:3002/lib/nicEdit/nicEdit.js?1225149103, 235-237

According to David Baron, from what I understand, these reports mean there are memory leaks in FF.

Unfortunately Leak Monitor will point me to general function calls that get applied to all functions, and the lack of a call stack makes it hard to find the pattern in the code.

I have been trying to narrow down the memory leak issues to identify the pattern that trigger them, but without real success.

I had more useful information using Drip from Joel Webber, but it is specifically designed for identifying object leaking in IE chrome, not FF.
(Reporter)

Comment 1

9 years ago
Created attachment 345770 [details]
Log Report from Leak Monitor 0.4.2 after closing a random itemize window
(Reporter)

Comment 2

9 years ago
small errata:

By According to David Baron, I mean according to Leak Monitor's website: "The things that are exposed to Web pages are definitely things that shouldn't leak, and most of those bugs are close to being fixed", which dates back from 2006

Comment 3

8 years ago
Stop bothering developers with this minor problem, you are the only one, who has it

Comment 4

8 years ago
excuses for comment 3, some is spamming various bugs, see bug 567347
Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to the developer's website and download the latest version from there. If you no longer see this issue, please close this bug as RESOLVED, WORKSFORME. If you do see the bug, please post a comment.
Whiteboard: [CLOSEME 2010-12-01]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.