Re: [GD-Windows] Nasty GUI bug

[Mickael P. <mpo...@ed...>]

> Hi, 
> 
> I would say it is a problem of memory, but not of
> resources. As Javier had just point out, a resource
> leak is not fixed once you kill the application.
> Yesterday, I had the same kind of corruption : drawing
> the GUI of any of the open application was taking
> ages... The Task manager show me CodeWarrior was using
> 500 Mg, and that there was more than 1 gigaoctet
> used...
> Once I killed CodeWarrior, everything was OK again...

<rant>
Killing CodeWarrior generaly solve a lot of things...
</rant>

Well, more seriously, in my experience resource leaks
were fatal under windows 95/98 (millenium also I suspect),
but not always under windows 2k. Depending which kind of
resource was abused 2k sometimes manage to restore it's
internal state when the abusing program is killed, for some
other kind of resources he does not manage to do it.

By resource I mean things like file system handles, gui
items, and basicaly all these things you have to allocate
and then release but are not necessarily related to memory.

The worse problems I had were with DLL, because of the 
reference counting thing you not always manage to free
it from memory, so the lost resources I still considered
as used.

    Mike