On 27 Jun 2012, at 19:28, Mikhail Tchernychev <[email protected]> wrote:
> There is also other tool, valgrind, widely used under Linux. Yes, we are familiar with valgrind, and FLTK is checked with it fairly often. Be aware that interpreting the output of such tools is quite tricky. Are you sure you know how to discriminate between leaks, and the normal runtime footprint of the code? Note that allocations that are made when the app starts, and are not free'd until the runtime releases them on app exit are *not* leaks. Similarly, it is not always a leak if a widget destructor is not called. It is only a leak if the memory footprint increases over time due to memory management. AFAIK there are currently no leaks in FLTK. If you have evidence to the contrary, please post an STR detailing your findings and the steps to reproduce, so that we can investigate further. Thanks... -- Ian Sent, much to my surprise, from my iPhone _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
