Re: [GD-Windows] Nasty GUI bug

[<e_a...@ya...>]

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...

Emmanuel


 --- Mickael Pointier <mpo...@ed...> a
écrit : > > Pierre Terdiman <p.t...@wa...>
wrote:
> >
> > > I didn't say that, but maybe that was unclear.
> I'm running W98 but
> > > the bug *does* indeed occur on other machines,
> e.g. with W2K.
> >
> > The only way I have ever managed to corrupt the
> Win2K GUI was by creating
> > graphics resources and not deleting them: bitmaps,
> DCs, fonts, etc. The
> last
> > time I had this was because I was creating a new
> bitmap every time the
> > window was resized / redrawn, but not freeing the
> previous bitmap
> properly.
> 
> I second that.
> 
> This kind of behavior is generaly not memory
> related, but "resource"
> related. You can kill a windows 98 simply by doing a
> loop that call
> "CreateWindow" repetetively.
> 
>     Mickael Pointier
> 
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Gamedevlists-windows mailing list
> Gam...@li...
>
https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
> Archives:
>
http://sourceforge.net/mailarchive/forum.php?forum_id=555 

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com