Someone had found a memory leak and when I ran XCODE analyzer I found a few possible culprits.
XCODE analyzer stated that there were three possible sources for memory leaks. 1) early returning without releasing the CGImageDestinationRef destination. 2) returning with out releasing destination in the CGIMageDestinationFinalize==false case 3) The naming convention of the ImageWithScale method should be CreateImageWithScale or CopyImageWithScale since we return an owned +1 retaincount CFObect. 3) May be just a break in convention (only used to notify users of the api), however XCODE analyzer seems to think it might be a problem.
Someone had found a memory leak and when I ran XCODE analyzer I found a few possible culprits.
XCODE analyzer stated that there were three possible sources for memory leaks. 1) early returning without releasing the CGImageDestinationRef destination. 2) returning with out releasing destination in the CGIMageDestinationFinalize==false case 3) The naming convention of the ImageWithScale method should be CreateImageWithScale or CopyImageWithScale since we return an owned +1 retaincount CFObect. 3) May be just a break in convention (only used to notify users of the api), however XCODE analyzer seems to think it might be a problem.
thanks