Re: Memory Leaks?
From: Ken Gardner (KenGardner_at_discussions.microsoft.com)
Date: 02/28/05
- Next message: Mike Hall \(MS-MVP\): "Re: CA vs. Symantec vs. Microsoft"
- Previous message: JayJay: "Re: Logging in on Windows XP Pro"
- In reply to: Tim Slattery: "Re: Memory Leaks?"
- Next in thread: Tim Slattery: "Re: Memory Leaks?"
- Reply: Tim Slattery: "Re: Memory Leaks?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 28 Feb 2005 09:51:03 -0800
"Tim Slattery" wrote:
> >What is memory leak? Does it ever leak? What cause memory to leak? Someone
> >had asked me yesterday and I wasn't able to give him a clear answer.
> It's a programming mistake. Programs constantly obtain memory from the
> operating system. Generally, when they finish with it they are
> supposed to return it. If a program asks for memory but doesn't return
> it when it finishes with it, the memory has "leaked". If this keeps
> up, eventually the program will ask for memory and be told that there
> isn't any.
Just to be clear, what is supposed to happen is that when an application is
closed, the application code may still be in the system cache (assuming
sufficient RAM, of course), but it should no longer be taking up the memory
used for applications, right?
- Next message: Mike Hall \(MS-MVP\): "Re: CA vs. Symantec vs. Microsoft"
- Previous message: JayJay: "Re: Logging in on Windows XP Pro"
- In reply to: Tim Slattery: "Re: Memory Leaks?"
- Next in thread: Tim Slattery: "Re: Memory Leaks?"
- Reply: Tim Slattery: "Re: Memory Leaks?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|