It was a dark and stormy night when REM said:
J44xm <
[email protected]_g> wrote:
Firefox currently has a memory leak that causes it, on my system,
to use up to 60 MB of RAM sometimes. Another user suggested a
freeware program called RamBooster to help free up RAM.* Before I
try it, I thought I'd see if anyone had any experience with this
program, and check to be sure it's what I need.
[Snip]
When I ran 98SE I used 'RamIdle' and it worked wonderfully! I
never had any resource or memory problems. I don't run things like
Norton, which usurp beyond help though. [Snip]
For me using 98SE, this was the most valuable program on the
machine. I've read many articles that state these utilities are
useless. I disagree. It made 98SE run like my XP machine does now,
simply no resource/memory problems at all.
With all due respect I totally disagree with you about memory
managers.
Two comments:
First the comment with less weight is my personal experience with
RamIdle.
After reading your message I was very curious about RamIdle and I
wanted to try for myself just to see it doing its 'magic'.
Plus as a student of software development (albeit a very raw one) I
thought that creating a bad developed application would be a very
interesting learning exercise, I mean, creating a very simple
application that only leaks memory is not the theme of many win32
tutorials/textbooks. ;-)
Anyway. I downloaded and installed RamIdle 4.8.2 (standard) and
rebooted my PC (MS Windows 98 First edition + Celeron 400 MHz + 32 MB
RAM). Then I started SciTE, MS Resource meter, RamIdle and the
leaking app.
System/User/GDI resources as shown by MS resource meter and RamIdle
were going down at a consistent pace (about 2%-3% about 20-30
seconds):
- about 80% -
So far RamIdle did nothing automatically so I clicked on its systray
icon and selected 'Free up 2/4/8 MB' a few times but it did nothing.
- about 60% -
mmm ... Maybe RamIdle can only recover memory leaks when the faulty
app is closed? Just to be sure I closed the leaking app and waited
for a moment but nothing happened, then I selected (again) 'Free up
2/4/8 MB' a few times but there was not noticeable effect. I started
the leaking app again.
- about 30% -
Trivia: can you guess what happened? ;-)
- about 20% -
Again no noticeable effect by RamIdle either automatically or by
selecting the options 'Free up 2/4/8 MB'
- below 10% -
The systray icon of RamIdle was being shown with a 'X' and I got the
dreaded message 'Insuficient system resources, close some running
apps, MS Windows could stop responding, etc, etc, etc' so I just
closed all the apps and rebooted the PC.
Summary: my personal experience is that RamIdle is unable to do
anything to stop a memory leak.
Second comment (the one that counts ;-):
Of course the key issue about memory managers is what proficient and
respected programmers/jornalists say about this kind of applications:
Fred Langa has a negative opinion about them:
<
http://www.informationweek.com/
story/showArticle.jhtml?articleID=17200583>
Mark Russinovich (SysInternals) said they are a hoax:
<
http://www.winnetmag.com/Windows/Article/ArticleID/41095/41095.html>
Radsoft is even more extreme and call them 'rainmakers':
<
http://radsoft.net/resources/software/reviews/redux/>
On the other side of the fence I have not found (yet) a 3rd party
article from someone of the level of Steve Gibson/Robin
Keir/SysInternals/Radsoft/Fred Langa saying good things about memory
managers.
So IMHO memory managers are just a waste of time.