Hi,
I checked out the sample and it is actually a bug in our binding (I also
filed a bug: https://bugzilla.xamarin.com/show_bug.cgi?id=7117 - you can CC
yourself to get notified when it's fixed).
You could manually call release on the leaked object:
using MonoTouch.ObjCRuntime;
var result = context.CreateCGImage (output, output.Extent);
Messaging.void_objc_msgSend (result.Handle, Selector.GetHandle ("release"));
but note that this workaround will crash once the issue is fixed.
Rolf
On Wed, Sep 12, 2012 at 2:10 AM, couchworx <[email protected]> wrote:
> Hi Rolf,
>
> thanks for responding.
>
> profiling the "Adjust Contrast and Brightness of an Image" recipe App
> "Color_Controls_Pro" every call to HandleValueChanged up to the crash (7
> calls, 8 snapshots) shows no increase of object count or total memory used
> after the first one. I've attached the output document.
>
> 1 ObjCount 1,384 Total Mem 36,528 bytes
> 2 ObjCount 1,622 Total Mem 42,600 bytes
> 3 ObjCount 1,628 Total Mem 42,736 bytes
> 4 ObjCount 1,630 Total Mem 42,784 bytes
> 5 ObjCount 1,630 Total Mem 42,800 bytes
> 6 ObjCount 1,630 Total Mem 42,800 bytes
> 7 ObjCount 1,630 Total Mem 42,800 bytes
> 8 ObjCount 1,630 Total Mem 42,800 bytes
> crash
>
> http://monotouch.2284126.n4.nabble.com/file/n4656965/profiler-output.mlpd
> profiler-output.mlpd
>
>
> Can you explain why and when to Dispose Images while in use?
> Disposing the Image while having it shown to the user does not seem to make
> sense to me ... ;-)
>
> thanks
> Boris
>
>
>
>
> --
> View this message in context:
> http://monotouch.2284126.n4.nabble.com/CoreImage-Memory-Consumption-Recipe-affected-tp4656953p4656965.html
> Sent from the MonoTouch mailing list archive at Nabble.com.
> _______________________________________________
> MonoTouch mailing list
> [email protected]
> http://lists.ximian.com/mailman/listinfo/monotouch
>
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch
