Resource Leak

Hi Ramona

You've just reported a possible fix for resources leak in NS 7.1 on your Netscape page.

Does this revision also apply to 7.x versions? My resources seem to erode much more swiftly when I'm using NS 7.02 than I've observed with other software. My imagination: I don't know. I figured that it had something to do with Cache buildup which sure consumes HD space at a rapid rate - temporarily - but I clean it every night and the memory cache periodically...when I think of it!

Thanks

 

Hi Welt,

Yes, you can apply the workaround to Netscape 7.02. BTW, I have been working on some of my pages today, and have added a couple of things to that page, so you may want to take another look:
Netscape 7.1 Resource Leak.

If you want to check your Cache settings: in the Location Bar, type in "about:cache ". This will show your Cache information, and will even list the entries.

Ramona

 

Hi Ramona

Thanks for the quick reply. I'll check out the additions to your NS page tomorrow. it's getting late.

That tip to read cache entries and what they are is quite something. I opened NS and came straight to Windows BBS from my Personal Tool Bar, scrolled to my message and your reply. ..only. I cannot believe the cache entries. If I looked closely I swear I'd find the kitchen sink.

Good thing I came here. It's the first time I think that I've ever had a reply and not been notified by email. ;-(

Enjoy your weekend.

 

Hi Welt,

haven't checked Ramona's pages lately, but with Netscape 7.02, you should be able to set the memory cache size within Netscape, preferences by going to Edit Prferences Advanced Cache, then set the Memory Cache siize there. I'm currently using Mozilla 1.0.1, which is basically Netscape 7.01. I stil have that setting. Netscape 7.02 is basically Mozilla 1.0.2.

Netscape 7.1 is based on Mozilla 1.4 which is the Mozilla "trunk ", a different development path from the 1.0x "branch ". Near as I can tell, the memory cache setting in the UI disappeared after Mozilla 1.3 and is no longer available in Netscape 7.1/Mozilla 1.4 because the memory cache is set automatically based on installed ram. That's where the workaround comes in

I suffered from a resource drain in both Netscape 4.79 and Mozilla 1.0.1 if I had my memory cache set too high. With Mozilla 1.0.1 I've found that lowering the default 4096 setting to 3000 kb in Edit Preferences Advanced Cache, for Memory Cache. works out for me and I no longer have the problem of system resources dropping.

Before I found the correct setting for my particular system(Win95, 64mb ram) , I was using the "clear memory cache" button periodically to restore system resources to the "green" (I have the Windows resource meter running all the time).

Anyway, I found the following background information:

(copy/paste)
http://bugzilla.mozilla.org/show_bug.cgi?id=204374

comment#65
I don't think it's a new problem, but fixing bug 105344
has made it worse. Since the memory cache is now much larger than before (mine went from the default 4MB
to 9MB), we'll keep many more GDI-resoruces in memory.

(copy/paste)
http://bugzilla.mozilla.org/show_bug.cgi?id=105344

Comment #60
This fix may be the cause of a SERIOUS new bug 204374 on Windows 9x machines.
It's setting memory cache so high that too many GDI resources are tied up.

 

Thanks Alice but my NS 7.02 already has the cache set at 2048K as recommended* by Ramona. [*as first trial].

Actually, my User and GDI resources seem quite well under control but I'm always seeking to improve them. NS does consume considerable but it also returns most when its shut down and I think this is what really important.

I have 320MB of RAM so am not suffering.

 

Hi Welt,


What I meant was, you don't need to use the user.js cache setting "workaround" if the Memory Cache size can be changed within Netscape's Edit Preferences Advanced Cache area.

Glad you've found a cache setting that works for you....

System resources are used up just as quickly with 64MB ram as with 320 MB ram. One has nothing to do with the other

In fact, with Netscape 7.1 the more ram you have installed, the higher the Memory cache setting that is automatically set, and the faster you run out of resources, in Win9x systems. That's where the cache workaround comes in, resetting the value downards via a line in the user.js file.