Exactly. I've been studying "Thinking in C++", in an attempt to learn
something, and the guy practically harps on memory leaks. "Watch out
for this bug, because it will give you a memory leak..."
I had always kind of thought that the OS was responsible for allocating
memory - what's the mechanism of a memory leak? Is it that the app
will request memory from the OS and not return it? In other words,
will the OS free all of the memory that the crappy app forgot to
release, or is it gone until you reboot?
The OS can't possibly know the app is done with the memory it's
allocated until the app releases it. If it doesn't, it's a memory
leak. The memory *may* be returned to the pool when the program
terminates, or maybe not.
I don't believe that's a memory "leak", per se. A "Memory leak" isI read in sci.electronics.design that Keith Williams <[email protected]>
wrote (in <[email protected]>) about 'best
schematic capture/board editor program to learn for professional
world?', on Tue, 13 Sep 2005:
I understand that apps can also leak into areas of memory that they have
no business to be writing to.
I read in sci.electronics.design that Keith Williams <[email protected]>
wrote (in <[email protected]>) about 'best
schematic capture/board editor program to learn for professional world?',
I understand that apps can also leak into areas of memory that they have
no business to be writing to.
John said:I read in sci.electronics.design that Keith Williams <[email protected]>
wrote (in <[email protected]>) about 'best
schematic capture/board editor program to learn for professional
world?', on Tue, 13 Sep 2005:
I understand that apps can also leak into areas of memory that they have
no business to be writing to.
If a program requests memory and does not return it when finished, it's
the program's fault. If this leak causes the OS to crash because it
hands out memory continuously until it falls over, it is the OS's fault
(as windows may do). If the OS doesn't automatically free all the
program's memory when it is killed, then you are the proud owner of Win9x!
That's only possible if the OS doesn't properly implement memory
management and inter-process security. In other words, it happens on
Win9x, but not on WinNT (including W2K and XP) or real OS's.
David Brown wrote...
Yes and no. If I close all my open programs, Win-XP sometimes recovers,
but not always; frequently a reboot is required. The operating system
may indeed restore the lost memory if the application is terminated, but
I know many applications are rarely or never terminated. Whatever the
explanation, the painful scourge of memory leaks is alive and kicking.
Interesting factoid, my computer running Win-XP is far less stable than
my computer running Win-2000. This wasn't true at first, but degradation
of my Win-XP computer set in rapidly. BTW, it's treated with kid gloves,
behind a firewall, doesn't even run an email program, full security progs.
Fat chance of finding a PDF reader that works, and isn't written byYep. Watching other's experiences with XP, I've stuck with Win2K.
...Jim Thompson
Fat chance of finding a PDF reader that works, and isn't
written by those Adobe wankers?
Yes and no. If I close all my open programs, Win-XP sometimes recovers,
but not always; frequently a reboot is required. The operating system
may indeed restore the lost memory if the application is terminated, but
I know many applications are rarely or never terminated. Whatever the
explanation, the painful scourge of memory leaks is alive and kicking.
Interesting factoid, my computer running Win-XP is far less stable than
my computer running Win-2000. This wasn't true at first, but degradation
of my Win-XP computer set in rapidly. BTW, it's treated with kid gloves,
behind a firewall, doesn't even run an email program, full security progs.
Hello Winfield,
Tell me about it. For the new lab PC they didn't give me a joice
anymore. No, couldn't "downgrade" to NT this time, I had to accept XP.
What a pain.
The worst is the persistent bugging for attention by bubbles. They threw
in McAfee and it constantly splashes a stupid window over anything you
are working on. "Your computer needs an update and is in danger
blah...blah...blah". I turned everything off I could, didn't get rid of
it. Next is an un-install I guess.
Same here. Not happy with XP at all. In the end none of these "operating
systems" is as good as DOS.
Regards, Joerg
thought it'd be best to get a second opinion, though I expect he knows
what he's talking about. What do you all think? Thanks,
I chose NONE for OS, and put Win2K on all three ;-)
Jim Thompson
When I last bought PC's, 3 last summer, they only offered XP. I chose
NONE for OS, and put Win2K on all three ;-)
...Jim Thompson
John said:Both my new Dells came with XP/SP2 installed. A number of things about
XP are stupid and annoying, but they are very reliable and seem to run
fine for weeks at a time. The Dells themselves are crap, at least as
far as packaging and ergonomics go.
John
Interesting factoid, my computer running Win-XP is far less stable
than
my computer running Win-2000. This wasn't true at first, but
degradation
of my Win-XP computer set in rapidly. BTW, it's treated with kid
gloves,
behind a firewall, doesn't even run an email program, full security
progs.
martin said:Fat chance of finding a PDF reader that works, and isn't written by
those Adobe wankers?
Winfield Hill said:Interesting factoid, my computer running Win-XP is far less
stable than my computer running Win-2000. This wasn't true at
first, but degradation of my Win-XP computer set in rapidly.
BTW, it's treated with kid gloves, behind a firewall, doesn't
even run an email program, full security progs.
Hello Win. Are you by any chance suffering the XP GDI
Objects bug? This is where various lumps of software
request, and are assigned, GDI handles. The bug allows
some software to acquire thousands of handles, which
drastically slows down the computer.
To look at this: Move to an empty space on the icon bar
along the bottom, right-click, and select 'Task Manager'
from the menu.
From the TM menu select 'processes', then 'view'. In the
view menu, select 'columns', and untick everything except
'user name' and 'GDI Objects'. OK/close the view menu.
The processes window should now show a listing of software
names, who is the user of that software, and the count of
GDI objects assigned to each. Each count should be in the
10's for most software, with just a few 100's.
Make a rough mental record of the counts, and minimise the
TM window. Throughout the day, open up the TM window and
check to see if any software is grossly accumulating handles.
For example. I'm monitoring a particular prog. When loaded
it has 95 GDI Objects assigned to it. When doing a certain
action it gets about 10 more, but when closing the action it
does not release them. In just a few minutes it is up to
about 270, and people have reported 8000-10000 at the end of
the day.... XP running seriously slugged.
I believe that Microsoft have issued a fix for this.
Tony Williams said:I believe that Microsoft have issued a fix for this.
