SillyDog701

[beanboy89]

The Mozilla Corporation has released Mozilla Firefox 1.5.0.1. Firefox 1.5.0.1 address a few stability and security concerns, including these:

Here's what's new in Firefox 1.5.0.1:

* Improved stability.
* Improved support for Mac OS X.
* International Domain Name support for Iceland (.is) is now enabled.
* Fixes for several memory leaks.
* Several security enhancements.

Downloads:
Windows Installer
Linux tar file
Mac OS X Disk Image

FTP Directory Mirrors

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

[profman]

It would be nice if this release fixes the "memory hog" problem that was experienced by some Firefox 1.5 users. Some people are a bit unhappy about the Mozilla organization's apparent "no comment" approach to the memory problems of the 1.5 release of Firefox.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915

[Mandrake]

Thanks. Downloading this now.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8) Gecko/20051111 Firefox/1.5

[Mandrake]

I haven't seen any difference in memory usage between 15.0.1 and 1.5. Uses about 24mb of ram with one tab, and goes up from there. With eight tabs open it was happily using upwards of 50mb of ram.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

[Fulvio]

Considering that I have at least four tabs with each program, it looks ok to me if it is near 45 MB. I removed two extentions, but still have six tabs, I dropped from 58 to 44 MB on starting. Is it leaking? Only time will tell.
And, although others have complained of the time that it takes to load, I consider it unusually fast.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

[jksteinhauer]

As usual the folks at work at Mozilla keep this moving upward and onward. I was able to update using the update feature and update my extensions as well. Am still waiting on media plug ins' page to be accessable; currently the page won't load for me here - namely needing to update media plug ins which never worked after I upgraded to 1.5 from a previous version.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

[Fulvio]

Jk,
which media plugins? In case you do not know, or remember plugins reside in the plugins folder, and unless you are using a previous plugins folder, or reinstall the media players, they will never do any updating. This is the way things work. With a new program, you get a barebone plugins folder, but any plugin folder from NS7.2, or other related programs can be copied and pasted it. You may have to deletethe npmozax.dll plugin (for WMP activeX playing). With that exception you do not need any update.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060115 K-Meleon/1.0

[Pu7o]

Also, I note that, since Firefox 1.5.0.1 is identical to RC1, the users of Firescape 0.1 are already up to date with the latest Firefox core.

UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8) Gecko/20060118 Firefox/1.5.0.1 Firescape/0.1 wml/1.3

[James]

FF has IE 7 beat by a country mile. Right now with four tabs open I'm using 83,408 K of RAM. Nice, eh?!

UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

[Pu7o]

Type "about:config" in your location bar, then create a new integer called browser.cache.memory.capacity with content 16384. That should stop the memory leak.

UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8) Gecko/20060118 Firefox/1.5.0.1 Firescape/0.1 wml/1.3

[James]

Okay... I need a bit more direction on this. What do you mean by creating an integer? Where do I create it and what exactly do I do with it? Remember now... I'm just an ordinary kinda guy with very little computer smarts. I'm all ears though if you can help me tighten up the memory leak. And we are talking about IE 7, right?

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

[Pu7o]

Well, first go to the URL bar (where you'd type a website), and type [tt]about:config[/tt] there.
Then, in that list of strings you have there, right-click and create an integer, like this:



The following dialog should pop up, and fill it like in the screenshot:



Another dialog should appear, insert the number like so:



Then, restart Firefox and you should have no more memory problems.

UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8) Gecko/20060118 Firefox/1.5.0.1 Firescape/0.1 wml/1.3

[beanboy89]

And we are talking about IE 7, right?

Pu7o is refering to Firefox.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

[Edward]

Type "about:config" in your location bar, then create a new integer called browser.cache.memory.capacity with content 16384. That should stop the memory leak.

Would something like this work when using SeaMonkey on a slower computer (running Linux), in order to speed it up?

UserAgent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.9a1) Gecko/20060124 SeaMonkey/1.5a

[Pu7o]

It doesn't speed up firefox/seamonkey at all, in fact, it makes it slower, by limiting the memory that it can use.

UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8) Gecko/20060118 Firefox/1.5.0.1 Firescape/0.1 wml/1.3