Re: kaa-metadata + gtk main loop + subprocess = when child exits, 100% CPU usage

On Fri, 2010-12-24 at 13:24 -0300, Juan Manuel Santos wrote:
> I think I get what I am doing this, I am kind of integrating kaa's main loop 
> inside GTK (or calling GTK's from inside kaa?). Anyway, besides these three 
> lines of code I touched, is there any implication for doing this? For example, 
> will gobject.idle_add function keep working?

When kaa.main.run() is called after pygtk is imported, it will use gtk's
mainloop under the hood.  It actually calls gtk.main_iteration_do().  So
idle functions should continue to run.  It should theoretically work
exactly like the standard gtk mainloop. :)

But it's a bug that this is necessary.  I guess I never ended up fixing
the original problem (that signals get hooked at import time).  I
understand why you're seeing the 100% cpu usage problem and it shouldn't
be too difficult to fix.

I'll see about sorting this out after Christmas.

Cheers,
Jason.


------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl