DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2185 Version: 1.3-current The interesting thing is that this memory is not "completely lost" e.g. program stores pointers to that chunks till the end of execution. So I had to turn on valgrind ability to log even "still reachable" chunks, therefore log is so big. So it seems that fltk just incorrectly caches some resources. Something like when it should take some object from the cache it creates it again and caches again. I am complete noob in fltk's internals so this may sound weird. But maybe it will help. Link: http://www.fltk.org/str.php?L2185 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
