More or less.
It appears that since the documentation in NSBundle does not state that its
thread safe, it isn't.
From Core Animation tho, it would appear that executing a CATransaction flush
may have resolved my original message, but perhaps not the problem.
If I read this correctly, this
On Thu, Sep 6, 2012, at 09:09 AM, John MacMullin wrote:
More or less.
It appears that since the documentation in NSBundle does not state that
its thread safe, it isn't.
This really isn't the whole story. NSBundle isn't thread-safe (don't
send it messages from multiple threads), but is
On 9/5/12, John MacMullin john.macmul...@cox.net wrote:
I am getting the following message: CoreAnimation: warning, deleted thread
with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment
to log backtraces.
What in general would be causing this?
Just another data point
I am getting the following message: CoreAnimation: warning, deleted thread
with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to
log backtraces.
What in general would be causing this?
How do I set CA_DEBUG_TRANSACTIONS=1?
Best regards,
John MacMullin
On Wed, Sep 5, 2012, at 03:35 PM, John MacMullin wrote:
I am getting the following message: CoreAnimation: warning, deleted
thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in
environment to log backtraces.
What in general would be causing this?
In general, it would
CA_DEBUG_TRANSACTIONS=1 in
environment to log backtraces.
What in general would be causing this?
In general, it would be caused by deleting a thread with an uncommitted
CATransaction. ;-)
How do I set CA_DEBUG_TRANSACTIONS=1?
It's an environment variable. Set it in the Environment
On Sep 5, 2012, at 4:12 PM, John MacMullin wrote:
Ok, I went to the scheme in Xcode and added the variable. Running again
produced the following backtrace.
0 QuartzCore 0x7fff8a736b95
_ZN2CA11Transaction4pushEv + 219
1 QuartzCore
Ok, that was it. I loaded [NSBundle loadNibNamed:XXX] in a background thread.
Fixing that problem resolved the message.
Thanks.
On Sep 5, 2012, at 4:13 PM, Kyle Sluder k...@ksluder.com wrote:
On Sep 5, 2012, at 4:12 PM, John MacMullin wrote:
Ok, I went to the scheme in Xcode and added the
On Sep 5, 2012, at 5:13 PM, John MacMullin john.macmul...@cox.net wrote:
Ok, that was it. I loaded [NSBundle loadNibNamed:XXX] in a background thread.
Fixing that problem resolved the message.
Did the process of fixing it also illuminate other areas you seem to be hazy
on, such as how Core
