Closed Bug 281136 Opened 21 years ago Closed 20 years ago

Mozilla browser eats the memory until it is killed by the system

Categories

(SeaMonkey :: General, defect)

1.7 Branch
x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: al_pavel, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041219 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041219 By clicking on "Advanced Mass Sender 4.2" link under http://www.getserial.com/index.php?search=a&nn=12 , mozilla eats memory until it is killed by system. I'm not able to do everything to stop it. "top" shows over 1 Gb VIRT memory consumed by mozilla-bin. Reproducible: Always Steps to Reproduce: 1. Open http://www.getserial.com/index.php?search=a&nn=12 2. Click on "Advanced Mass Sender 4.2" 3. Enjoy it, you will not be able to do everything until the system kills mozilla thats eats memory and swap continuously :) Actual Results: Mozilla eats memory and is after 30 seconds killed automatically. Expected Results: Mozilla opens new browser window.
The system: Slackware Linux 10, Mozilla compiled from source (from mozilla.org, no patches). AdBlock, Flashblock and SessionSaver extensions and Flash Plugin 7.0 installed. Other people says that the same behaviour have mozilla 1.7.2 under SuSE 9.2 and Firefox 1.0 but not always (sometimes the browser behaves correctly on this page).
Worksforme with a current trunk build....
Version: unspecified → 1.7 Branch
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.