Mozilla 1.4

Hey there,


Does 1.4 have a resource leak like NS 7.1? and if so do I need to use the same workaround as I did for NS useing the User.js file?

Regards,

FireDancer

 

Yes, the same leak exists. Netscape 7.1 is based on Mozilla 1.4, and as a result has the same problem.

tranquilo

 

And, same fix applies.

 

Hi Firedancer,

I've posted new information on the resource leak since you last posted on this issue: Resource Leak in Netscape 7.1

This is the better/newer way to add the memCache setting, remembering to back up the prefs.js file first:

Back up the prefs.js file

Clear the Location Bar and then type in: about:config
Scroll down and look for browser.cache.memory.capacity
It shouldn't be there, but if it IS, right click, pick modify, and change to 4096, 2048, or 1024.
(After much experimenting, I have found 1024 to be the best setting.)

If the setting isn't there:
Right click
Pick NEW
Pick INTEGER
Type in: browser.cache.memory.capacity
Click OK
Type in 4096, 2048, or 1024
Click OK
Restart Netscape (or Mozilla)

This is the new way of editing Preferences, as offered in the newer Releases of Mozilla. The advantages are listed below, as mentioned in earlier threads by captjlddavis:

"Setting the user_pref( "browser.cache.memory.capacity ", 4096, 2048, or 1024);

The user.js writes to the prefs.js - and takes effect EVERY TIME you start NS.

In effect this will preclude any changes you make in about:config from becoming a "permanent" change.

Any change you make in "about:config" takes effect AND is WRITTEN to the prefs.js on exit....

When you re-start NS, any setting you make in user.js overrides the prefs.js (change from about:config) and nullifies the change and you are back to the original user.js setting.

For this reason I suggest that you make the entry in the "prefs.js" NOT the user.js - any subsequent change thru the "about:config" will be recorded in the prefs.js on exit.

For Advanced Users Only:
Further, if you want to make the change to become "default" setting and stop NS/Moz from calculating the cache size:

Add the following line to the all-ns.js file

pref( "browser.cache.memory.capacity ", 4096, 2048, or 1024); "

FWIW,

Ramona

 

Thanks so much all

wasnt sure... thought I would ask Thanks for the new info Ramona I appreciate it I also have found useing a setting of 1024 is much better

Regards,
FireDancer

 

Hi Firedancer,

I'm glad to hear the setting works for you! I'm very happy with it myself, because I really do like using all my tabs.

Ramona