294875 - Memory leak , xul remote application

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[insys]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Tested on remote XUL application.
Each time an instance of the new application window is opened, a certain amount of
memory is allocated, however, it is not released when the window is closed. 
If you keep opening and closing new windows, you can watch the memory 
allocated to 'firefox-bin' keep growing and growing.
If you disable all cache, the amount of used memory is bigger.


Reproducible: Always

Steps to Reproduce:
1. Open new xul application window
2. Close opened window
3. Check memory allocated to the firefox process  before and after


Actual Results:  
Memory kept growing, but never releasing each time I closed opened application
window.


Expected Results:  
Memory allocated to the new window should have released each time it was closed.


User-Agent:     Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414
Firefox/1.0.3
about:config
nglayout.debug.disable_xul_cache	true
browser.cache.disk.enable		false
browser.cache.memory.enable		true

Comment 1

[insys]

Attachment: testcase

Comment 2

[Kevin Brosnan]

Please recheck with a current nightly a lot of work has been done on Firefox's
memory usage bug 131456 was one of the bigger fixes.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

The 1.0.x versions of Firefox have not had any core improvements (like memory
handling) since August '04. Which make 1.0.x releases poor canidates for
reporting this type of bug.

Comment 3

[insys]

Comment on attachment 184078 [details]
testcase

You can simulate test with local installed MAB !

Comment 4

[Cignangulo [:cigno]]

Insys - your reported Firefox version(s) are too old a build to analyze bugs against now. The problem you are reporting may well have been fixed already.

Could you please download a recent version or nightly build from <http://www.mozilla.org/releases/nightly.html>, and then let us know if you still see this problem?

Many thanks, Cigno

PS: There are a number of memory leakage well documented and up-to-date bugs on the market. Please investigate whether this would become a dupe of one of them.

Comment 5

[Cignangulo [:cigno]]

Since there has been no reply to comment #4 ==> WORKSFORME. 

The reported Firefox version(s) are too old a build to analyze bugs against now. The problem you are reporting may well have been fixed already.

Could you please download a recent version or nightly build from <http://www.mozilla.org/releases/nightly.html>, and then let us know if you still see this problem? If so feel free to report back and ask for the bug to be reopened.

Many thanks, Cigno