What's up with these HUGE memory leaks on my 128MB system?

Madcowz

Platinum Member
Jul 23, 2000
2,652
0
0
Gosh I can't quite point a finger on the problem, but I just think it's my windows that's handling my 128MB of RAM horribly. I never had this problem till this new computer. I'll usually be running on about 30% resources but than occassionally It will just go down and down and hit a point where I can't open anything anymore. In fact right now I don't have enough resources to open my system properties to see the resources, and the last time I checked it was at 11%. It's so crazy b/c even after I close everything from ctrl+alt+del, the resources still remain so dangerously low... and I never have a lot open in the first place! I don't even play any games... I'll have a few IE browser windows open w/ scour exchange and my USB radio program in the background and that's it! If I want to open anything else I get resource errors, it's crazy! And I thought 128MBs was sufficient for just about anything... well It used to be until my blazing fast new computer. You think I wouldn't have a problem with a new installation of windows, but apparently not. If I don't get this fixed I might have to get another 128MB stick... but I would hate to do that b/c my CUSL2 might be difficult since I hear it's finicky with 2 sticks of RAM.
 

EvilDonnyboy

Banned
Jul 28, 2000
1,103
0
0
try installing windows again. what version fo windows dyo you have?

putting another ram stick will likely only prolong the time before you get resource errors, since this is a mem leak problem.

 

Madcowz

Platinum Member
Jul 23, 2000
2,652
0
0
I'm running on windows 98... I'll just wait to upgrade to winme instead of reinstalling 98
 

Lore

Diamond Member
Oct 24, 1999
3,624
1
76
I'll tell you right now it's most likely Scour Exchange.

We had a resident who couldn't do anything that was TCP/IP related. She couldn't check email, couldn't browse the web, etc. I could PING any host I wanted to, however. Loaded Netscape and it said "TCP/IP error: Not enough memory" so I thought maybe it was a memory leak issue.

Took a look at system properties, and sure enough, only 26% left for system resources. I started closing everything she had in her system tray, but it only brought it back to about 43%. Then I closed Scour Exchange (also on her system tray) and it went up to 74%. How's that for memory leak? :)

Give that a shot and let me know.
 

joeryu

Golden Member
Sep 14, 2000
1,678
0
0
get memturbo, nice little proggy that fixes up those memory leak problems.
 

cparker

Senior member
Jun 14, 2000
526
0
71
similar thing happened to me on a 128mb W95 system. Everything worked fine until I installed a cable modem along with aol 5.0. Aol promptly installed lots of multimedia stuff including realplayer. I also had a virus checker from ComputerAssociates that also was running. Leaks would occur when I was in aol doing some multimedia stuff. system would just run out of resources and die. I haven't bothered reinstalling anything yet, but now when I use that particular pc and I'm going to do anything involving aol I avoid doing the multimedia stuff. I just kill realplayer and a few of the other progs running in background that I dont' need after I boot up. I'll reinstall a new OS on this particular machine, but for the time being this works. If I do want to do multimedia I make sure I reboot after I'm finished and don't run other apps, especially IE5.5, in other windows.
 

bigshooter

Platinum Member
Oct 12, 1999
2,157
0
71
winme will kill your memory even worse. Don't know why but when my friend used mem turbo and monitored free memory, as soon as he defragged it or whatever it does it would show a lot of free memory. Then we let it sit there and it would just start using up memory. It was weird, as soon as I saw that I said screw games and put win2k back on.
 

Sir Fredrick

Guest
Oct 14, 1999
4,375
0
0
memturbo only helps by flushing your memory to the swap file at certain time/memory intervals, I believe. I'm also willing to bet that scour is the culprit, don't use it for a while and see if you still have the problem
 

Linux23

Lifer
Apr 9, 2000
11,370
741
126
LOL at Zippy! :)

No, when you get the BSOD, that's when Windows telling you it's working!
 

culex

Senior member
Jul 26, 2000
744
0
76
Yes, if you think resources are sucked less in WinME, think twice. It is the same thing going from Win95 to Win98. You need beefier systems!

128MB on WinME should feel the same way you'd run a Win98 machine with 64MB of RAM.

Resources are constantly drained no matter what... even when you open or close applications.

On top of that if you have tons of stuff loaded at startup and at backgrounds, it's inevitable.

Yea sure getting more RAM might help but even that'll still get drained. Just not as fast but it will get drained no matter what.

Go take an inventory of the items that load at startup and load the whole time at the background. Go uninstall what you feel you don't need. Also like someone mentioned, if you dont want to uninstall it, atleast get rid of it from registry by running MSCONFIG and Startup tab.

Not sure if the memory tweaks in Win98 helps the resource drain come down a bit but if you haven't done so, do the following.

Desktop -> right click My Computer -> Properties -> Performance -> File System... -> If the pulldown menu is set as "desktop computer" set as "Network Server"
Click OK and click Virtual Memory button...
Click let me specify blah blah...
Set the min and the max to twice your RAM size... which in your case is 256.
Also, if you have a second PHYSICAL drive that is barely accessed, it's better to leave the swap file there.

Someone mentioned memturbo. While I say "screw you" to all those applications that claim to fix your computer or optimize, and they just make it worse, MEMTURBO is an exception. Memturbo is great for your case... just don't overdo the recover amount.
 

Topochicho

Senior member
Mar 31, 2000
338
0
0
Win95/98/ME Does *NOT* unload a DLL once it is loaded. This is to speed up reloading of the program, but means bad things for you. That means, any basic memory leak within the program that called the DLL or in the dll itself does *NOT* go away once the program is shut down. Any other OS on the plannet (including NT & 2000) automatically frees the memory once the program shuts down, so most programmers (including Microsoft themselves) don't worry about minor leaks cause they will die with the program.

Scour may well be the culprit, but there are only a couple ways to really deal with the problem. Reboot 95/98/ME regularly. Possibly a MEM manager program can free those DLLS, or change operating systems. As I said 2000 doesn't have this problem and its one of the reasons nt/2000 is so much more stable. If you have to have 98 for gaming you might consider a dual boot machine.