Re: EXC_BAD_ACCESS on NSImageView::setImage
Re: EXC_BAD_ACCESS on NSImageView::setImage
- Subject: Re: EXC_BAD_ACCESS on NSImageView::setImage
- From: Volker in Lists <email@hidden>
- Date: Sat, 14 Mar 2009 20:37:28 +0100
Hi,
retainCount is not in anyway useful when debugging - I had many cases
of rc > 5 with the object being gone the next instance. your error
sounds like you loose the image at some point in time. retain it and
use Instruments to see if you leak or over alloc.
Volker
Am 14.03.2009 um 01:23 schrieb Dev:
On Wed, Mar 11, 2009 at 9:33 AM, Scott Ribe <email@hidden
> wrote:
Does your setImage method retain the image?
The object ExternalView is a NSImageView so the setImage is the one of
NSImageView.
The doc says nothing about it, but i added some debug log like this :
NSLog(@"BEFORE : %d", [NewDisplayImage
retainCount]);
[CameraView setImage:NewDisplayImage];
NSLog(@"AFTER : %d", [NewDisplayImage
retainCount]);
2009-03-13 17:17:35.105 xxx[2281:e503] BEFORE : 1
2009-03-13 17:17:35.106 xxx[2281:e503] AFTER : 3
So i guess the image have been retained 2 times ....
--
I.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden