From: John R. <jr...@ce...> - 2011-06-18 03:15:31
|
On Jun 17, 2011, at 7:17 PM, Chris Share wrote: > I'm not sure. The Guitarix developers say that they have fixed the problem but I > > haven't had a chance to test it. They said that: > >> A research brings up that OSX didn't support (but defined) unnamed semaphores, >> that's the reason why the gx_program_change_helper_thread blow up the CPU > usage. > > Cheers, > > Chris > > > ----- Original Message ---- > From: John Ralls <jr...@ce...> > To: GTK+-2 OSX Users <gtk...@li...> > Sent: Sat, 18 June, 2011 1:00:03 AM > Subject: Re: [Gtk-osx-users] Thread Question > > > On Jun 17, 2011, at 7:34 AM, Christophe Fergeau wrote: > >> On Fri, Jun 17, 2011 at 07:07:33AM -0700, John Ralls wrote: >>> Yeah, that's come up before. The GUI thread needs to be the first one >>> launched on OSX. I don't remember the details, but a search for "thread" >>> in comments on bugzilla.gnome.org (specify gtk and platform:macosx) >>> should turn them up. >> >> Is it https://bugzilla.gnome.org/show_bug.cgi?id=606378 ? >> (by platform:macosx, do you mean component:quartz?) > > > Yeah, that's the one. Sorry about mis-remembering component:quartz. > > Is that what's going on with Guitarix? Ah. Yes, that's true. Regards, John Ralls |