Opened 6 years ago

Last modified 9 months ago

#9458 assigned bug

Memory leak in BMediaFile -> BMediaTrack

Reported by: Robert S. Owned by: nobody
Priority: normal Milestone: R1
Component: Kits/Media Kit Version: R1/Development
Keywords: BMediaFile BMediaTrack memory leak Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All


I found a memory leak in BMediaFile -> MediaTrack. If you create a MediaTrack from BMediaFile, than release it again, close the media file and delete the media file object it is still some memory alloceted. I wrote a short test app (paladin project) to demonstrate the memory leak/bug, have a look to the method "DebugClass::TestMethod()" in the test app.

Attachments (1) (13.8 KB) - added by Robert S. 6 years ago.

Download all attachments as: .zip

Change History (6)

Changed 6 years ago by Robert S.

Attachment: added

comment:1 Changed 6 years ago by ttcoder

Just noticed your ticket after filing #9945 Robert.. Wondering, what metric do you use to know that memory is being leaked (not released) ? And does the leak still occur if you upgrade to hrev46028 or newer ? Seems that fix is in the "Reader" code rather than "Writer" code, but might as well try.

comment:2 Changed 4 years ago by pulkomandy

Still leaking in hrev48547.

comment:3 Changed 4 years ago by waddlesplash

Platform: x86All
Priority: highnormal

comment:4 Changed 2 years ago by axeld

Owner: changed from axeld to nobody
Status: newassigned

comment:5 Changed 9 months ago by jackburton

Could be related to the use of realloc() in BMediaFile::CreateTrack() (see #14329 ) or, in general, on how we allocate the BMediaTrack array in BMediaFile. ?

Note: See TracTickets for help on using tickets.