Bugs item #3267504, was opened at 2011-04-01 08:20
Message generated for change (Settings changed) made by carrier
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=3267504&group_id=55685
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Image File Tools
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: parki (lolwutlol)
Assigned to: Raman (rarora05)
Summary: split_open > split_close leaks memory
Initial Comment:
Brian, I've been doing some profiling and found that:
split_info->max_off is being malloc'ed at line 372 of split.c
But not free'd at split_close(). I haven't looked thoroughly to see if it breaks anything but it looks like a free() at line 322-323 solves it.
Also, I haven't experienced it so far, but it looks that code under the condition at line 403 of split.c (checking if an image name is a directory and returning NULL) isn't freeing memory either and would be leaking.
----------------------------------------------------------------------
>Comment By: Brian Carrier (carrier)
Date: 2012-05-09 14:00
Message:
I think these are all addressed in the new merged raw.c file from Rob
Joyce.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=3267504&group_id=55685
|
