Fwd: kaa-metadata + gtk main loop + subprocess = when child exits, 100% CPU usage
Juan Manuel Santos <[email protected]> Mon, 7 Feb 2011 17:18:53 -0300
| Newsgroups | gmane.comp.video.freevo.devel |
|---|---|
| Message-ID | <[email protected]> |
---------- Forwarded message ---------- From: Juan Manuel Santos <[email protected]> Date: Tue, Jan 25, 2011 at 6:57 PM Subject: Re: [Freevo-devel] kaa-metadata + gtk main loop + subprocess = when child exits, 100% CPU usage To: [email protected] On Fri, Dec 31, 2010 at 4:27 PM, Jason Tackaberry <[email protected]> wrote: > On Thu, 2010-12-30 at 17:08 -0300, Juan Manuel Santos wrote: > > Thanks for the info. I have already settled with option 3. Don't get > > your head too much into this since it's not kaa's fault. Nevertheless > > it's a good thing that kaa triggered this so we could find out. > > In any case, kaa.base svn should fix this issue. We now defer hooking > SIGCHLD until after kaa.main.run() is started, so we should no longer > trigger this pygtk bug just by importing kaa modules. > > Thanks for bringing this to my attention (again :)) > > 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 > _______________________________________________ > Freevo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freevo-devel > Hi Jason, sorry to bother you again. But today on my laptop I faced a similar problem. The software versions are the same as on my desktop (kaa-base/kaa-metadata trunk, GTK+-2.22.1, PyGTK-2.17.0). When running this test app ( http://www.vicarious.com.ar/~godlike/algo.tar.bz2) and trying to close it from the WM, it freezes. Last strace lines show this: http://paste.pocoo.org/show/326877/ The "Killed by SIGKILL" line corresponds to KWin killing the window since it's not responding. This also happens on the main app I was developing. I do not see this behaviour if I start and end the main loop from inside GTK+, only if I do so from within Kaa. Do you have any ideas as to what is causing this? I'm quite puzzled, since versions are the same as on my desktop. Thanks Juan Manuel Forwarding this to the list again in case it was not read. PyGTK-2.22 on my laptop still has the problem. The desktop is amd64 whereas the laptop is x86. Thanks in advance. Juan Manuel ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel