Re: Performance issue with new gtk 2.0 for win32

 Tor,

 Thanks for the reply. I will jkeep the list posted as I do more testing -- Let
me make sure I am not leaking anything on my app first (Valgrind on Linux does
not show leaks on my code -- It shows some unreachable mem in gtk/glib/libxml2
-- but I realy don't know if they are leaks . I al so am not able to execute
all the paths on my app on Linux, so it might be that I still have leaks in
other parts.

  Do you know why the momory goes up to 80 MB and then goes back down ? (Bill
also reported the same problem.)

  Thanks again.


--- Tor Lillqvist <[email protected]> wrote:
> >  1) Win NT Task MAnager is bogus (more likely)
> 
> No, I don't think so. The task manager is very useful as it can show
> the number of GDI and other handles allocated. Also, the amount of
> memory allocated with malloc() and friends is shown quite truthfully
> in my opinion, it goes up and down as memory is allocated and freed.
> 
> > 2) Gtk/GDK/GLIB libs free up memory chunks when they
> > age ???? (Unlikely huh?)
> 
> There were indeed memory leaks in GDK/Win32 in the previous builds
> (2.0.6), but they should be fixed now. At least, the test programs
> that are attached to the bug report
> (http://bugzilla.gnome.org/show_bug.cgi?id=79720) don't leak memory
> any longer, or didn't when I last checked.
> 
> Of course, it might well be that some other program still causes some
> memory leak in GDK/Win32, or even in the backend-independent parts of
> GTK+.
> 
> --tml
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com