On 28 Jul 2007, at 9:15, Benjamin Stauffer wrote: > Hey everyone. I'm working on my research project for college and > I'm trying to root out the memory leaks in my program. My program > collects data from a sound card and analyzes it. Unfortunately, > I'm getting a 192-byte memory leak, and I can't figure out where > it's coming from. > > I'm using fltk-1.1.x-r5891. I didn't see anything in the changelog > for the latest snapshot that looked like it would be the cause of > the problem, so I haven't gotten around to trying it. Also, I'm in > Windows using the MinGW compiler and the debug_new.c (Google "A > Cross-Platform Memory Leak Detector" to find it) as my memory leak > checker.
Can you post a minimal compileable example that manifests this bug? I don't have the time to check out and build your whole project, and I'm not sure the snippets you posted are showing us enough of the context... However, I'm reasonably sure the fltk timeout code doesn't leak - it's been attacked with valgrind etc. on supported platforms, and I have code that runs on XP built with mingw that does not appear to be exhibiting leakage after days of runtime... I am not familiar with the tool you used - does it discriminate between leaks and memory growth and so forth? I'm thinking it may be a false positive of some sort, or possibly some of the functions that the timeout calls may be a problem... -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
