Prev: Recycle Bin Not Empting
Next: svchost.exe
From: dennis on 6 May 2010 16:49
On 06-05-2010 21:38, henrikm wrote:

> I thought that was only true when you had some kind of garbage
> collection.
> If you allocate (and use) memory but loose your pointer and do not
> free the memory, does Windows really reclaim that memory upon
> termination without garbage collection?

Yes, the memory manager has full control over physical memory. So when a
process is terminated, it can do with the memory what it wants.
From: Dave Warren on 6 May 2010 18:40
In message
<732aff0f-1a4c-47c2-b210-b3b2ac8c548b(a)b7g2000yqk.googlegroups.com>
henrikm <henrik(a)majberger.se> was claimed to have wrote:

>> Once a leaking process is terminated, all memory becomes available for
>> others processes.
>
>I thought that was only true when you had some kind of garbage
>collection.
>If you allocate (and use) memory but loose your pointer and do not
>free the memory, does Windows really reclaim that memory upon
>termination without garbage collection?
>But it's been seven long years since I worked as a C/C++ developer, so
>I'm probably wrong... ;-)

Windows 9x was supposed to do this, although in practice it wasn't as
reliable as you might like. The NT kernel does release memory (and
virtually all other resources) properly when a process dies.
First  |  Prev  | 
Pages: 1 2
Prev: Recycle Bin Not Empting
Next: svchost.exe