Re: inconsistent crash drawing a string in a custom browser cell
Re: inconsistent crash drawing a string in a custom browser cell
- Subject: Re: inconsistent crash drawing a string in a custom browser cell
- From: Aki Inoue <email@hidden>
- Date: Wed, 7 Jun 2006 16:21:48 -0700
If the crash trace is consistent, that probably mean that you're
releasing the standard user defaults object.
Look for your usage of NSUserDefaults.
Aki
I added the code to run the draw in the main thread, but the app
can still be made to crash in exactly the same place.
Now I've been reading the threading guidelines and it states that
NSMutableAttributedString is not thread safe and I am allocating
and initializing these in my secondary threads, though no single
instance of one is ever accessed across more than one thread so I
am assuming this is OK. Or is that these non-thread-safe classes
should not be used at all in secondary threads or must be synced in
some way? the 'header' string in my cells is a
NSMutableAttributedString. I just alloc and init it. Each cell has
it's own.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden