#9945: BMediaFile leaks ca. 100 KB ------------------------------------+---------------------------- Reporter: ttcoder | Owner: nobody Type: bug | Status: new Priority: high | Milestone: R1 Component: Audio & Video/Codecs | Version: R1/Development Resolution: | Keywords: ffmpeg Blocked By: | Blocking: Has a Patch: 0 | Platform: All ------------------------------------+---------------------------- Comment (by ttcoder): Philippe indeed, if the entries from that table are somehow copied to somewhere allocated with new or malloc() then that could be it. I see the 'ffmp' constant set at line 149. Note to myself: if feeling like fishing in the dark later on, I could take a look at https://trac.ffmpeg.org/ticket/2937 I wonder if there is a way I could set a "watchpoint" in Debugger on a given heap area (rather than watch a given variable).. If yes then, knowing in advance one of the addresses of leaked memory blocks (from a previous run with printf() debug output ..etc) I could invoke debugger() at the beginning of main(), set the watchpoint on that address, click "Run" and get immediately notified (with an explicit backtrace) when that memory block gets malloc()ed. If I know who malloc()s it I'll have a good lead on who should be free()ing it yet fails to, probably. -- Ticket URL: <http://dev.haiku-os.org/ticket/9945#comment:4> Haiku <http://dev.haiku-os.org> Haiku - the operating system.