Hello, Now I'v some trouble on profiling swfdec, which uses glib heavily. The problem is that the gobject system registers many new types but never free them before program exiting. It is said that it's the OS responsibility to recycle those memory used by the gobject type system. But my memory checkers(profiling tools) don't like that. Any memory allocated during program executing but not freed before program exiting is marked as a "memory leak". So after a single run of swfdec, the profiling reports gave hundreds of "memory leaks" in the report. Many of them are happened inside the glib, though glib designers think they are not real "memory leaks" since they would be collected right after program exiting anyway. The difficulty here is it's hard to check which are real "memory leaks". Because memory leaks(if any) caused by swfdec are mixed together with those caused by glib in the final reports.
I'v googled related issue with glib, and it's seemed to be common problem with glib based apps and memory profilers. You guys have designed the smart GC mechanism in swfdec, so I guess you should have some good tips on profiling the memory leaks. Any suggestions? Thanks ahead. --zou _______________________________________________ Swfdec mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/swfdec
