Skip navigation.
 
mlRe: Quicktime/CoreImage memory leak
FROM : Fabien Roy
DATE : Sat Aug 12 23:24:29 2006

Try "OmniObjectMeter" found at:<http://www.omnigroup.com/developer/
omniobjectmeter/
>
Eval license at <https://store.omnigroup.com/cgi-bin/WebObjects/
OnlineStore.woa/wa/trial%3fproduct=bd595b063cd18000c697a13a
>

I was told that the "Boehm Garbage Collector" can be used, if 
installed, as a real good memory debugger, even used along a 
"reference count Garbage Collector"...

Hope that helps.



---
Fabien Roy
3426 N. 32nd Street, #64
Phoenix, AZ 85018, USA
<<email_removed>>
Tel:    602 476-1914
Cell:  602 312-2948


On Aug 12, 2006, at 1:46 PM, Daniel Hazelbaker wrote:

> Thanks for the thought, but MallocDebug does what leaks does, plus 
> a little better.  Specifically leaks does not include memory leaks 
> by Carbon API's (whats up with that?  A leak is a leak isn't it?). 
> Interestingly, leaks only shows a few minor things (as in a few K 
> instead of many MBs).  MallocDebug shows many MB, which leads me to 
> think all the lost memory is being allocated by NewHandle() and 
> there is something I am doing/not doing that is causing it not to 
> be freed. Grr.

Related mailsAuthorDate
mlQuicktime/CoreImage memory leak Daniel Hazelbaker Aug 9, 19:48
mlRe: Quicktime/CoreImage memory leak Christopher Hunt Aug 10, 01:58
mlRe: Quicktime/CoreImage memory leak Daniel Hazelbaker Aug 10, 05:11
mlRe: Quicktime/CoreImage memory leak Fabien Roy Aug 11, 13:25
mlRe: Quicktime/CoreImage memory leak Daniel Hazelbaker Aug 12, 22:46
mlRe: Quicktime/CoreImage memory leak Fabien Roy Aug 12, 23:24
mlRe: Quicktime/CoreImage memory leak Daniel Hazelbaker Aug 21, 22:33
mlRe: Quicktime/CoreImage memory leak Jonathan Grynspan Aug 21, 22:41