Re: [gtk-osx-users] CoreAnimation: warning, deleted thread with uncommitted CATransaction.
- From: Pascal <p p14 orange fr>
- To: John Ralls <jralls ceridwen us>
- Cc: gtk-osx-users-list gnome org
- Subject: Re: [gtk-osx-users] CoreAnimation: warning, deleted thread with uncommitted CATransaction.
- Date: Mon, 28 Dec 2015 19:07:52 +0100
Thanks John for your quick answer.
Well I was not aware of that rule!
I'm programming with GTKAda so I don't know if it is possible and how to "use idle events for
synchronization".
Do you know some examples?
Anyway, I will see on GTKAda list.
Thanks, Pascal.
http://blady.pagesperso-orange.fr
Le 26 déc. 2015 à 19:34, John Ralls <jralls ceridwen us> a écrit :
On Dec 26, 2015, at 8:53 AM, Pascal <p p14 orange fr> wrote:
Hello.
I've got issues with the following warning:
CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in
environment to log backtraces.
<...>
My program is multi-threaded with no problem since I upgraded to MacOS 10.11 and XCode 7.
In fact it's more than a simple warning because the thread is deleted.
There are some clues on:
http://stackoverflow.com/questions/12507193/coreanimation-warning-deleted-thread-with-uncommitted-catransaction
Is it a GTK-OSX concern? How to solve it?
Season greetings, Pascal.
http://blady.pagesperso-orange.fr
The SO article you cite indicates that this is a thread lifetime issue. One of the requirements of using
Gtk or Quartz in a multi-threaded environment is that all GUI operations take place in the main thread and
that other threads use idle events for synchronization. If you can create a simple demonstration program
that raises the warning within that constraint then by all means file a bug against gtk+, quartz backend.
Otherwise the problem is likely that your code violates the single-GUI-thread constraint.
Regards,
John Ralls
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]