Closed Bug 206772 Opened 22 years ago Closed 22 years ago

1.3.1 and 1.4b leak memory

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: stapel, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 WebWasher 3.0 Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4b/mozilla-win32-1.4b-installer-sea.exe I upgraded from 1.2.1 to 1.4b, and encountered massive memory leaks. (I use MemTurbo, so I could watch the memory being depleted.) I downgraded to 1.3.1, but still had the memory leaks (though not the crashes from 1.4b). So I have gone back to 1.2.1, and the memory leak is gone. (Plus, I like the splash-screen better. Do you think you could go back to the flaming dragon for newer releases?) Reproducible: Always Steps to Reproduce: 1. Open the browser. 2. 3. Actual Results: Regardless of whether the browser is open in the tray, whether I've surfed anywhere, or whether the browser is still running, memory dissipates. Using MemTurbo to scrub RAM is only stop-gap. I have to re-boot to kill whatever is munching the memory. Expected Results: Mozilla should sit still and behave itself, instead of acting like a long-lost son of Microsoft.
>Do you think you could go back to the flaming dragon for newer releases? No because we removed it because of copyright issues. You can very simple replace the splash if you put your own splash-screen in the Mozilla directory as "Mozilla.bmp" Follow the links in this page : http://themes.mozdev.org/splash.html Please try this : Uninstall Mozilla and manually delete the Mozilla application directory except the plugins subfolder and reinstall Mozilla. (the Mozilla profile is stored in a different location and will not deleted) Sorry but general leak-bugs are invalid unless you have an example URL. A mem-leak without a special URL is worksforme -> wfm
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.