Re: emelfm2 doesn't show exit codes for any child processes and uses 100% cpu

Since you mentioned glib i suddenly realised glib had been updated recently.
Turns out glib-2.12.5 (released 2 days ago) had a few bugs, one of
them was already fixed for my distribution (didn't solve the problem),
but then i saw this:

Overview of Changes from GLib 2.12.5 to GLib 2.12.6
===================================================

* Fix a configure test that was added in 2.12.5 to
 not declare every poll() broken

* Make GKeyFile accept keys that are commonly used

* Bugs fixed
354707 No return() in non-void function <=== THIS CAUGHT MY EYE
387260 hang in zenity
387823 glib 2.12.5 is breaking hal

* New and updated translations (ca,gu,mk,th)


So i locally bumped it to 2.12.6 (which was released a few hours ago).
And it works again. That's problem down.

Maarten.

On 12/20/06, Maarten Maathuis <madman2003@xxxxxxxxx> wrote:

For all commands that i know of. Even simple things like ls.

Maarten.

On 12/21/06, tpgww@xxxxxxxxxxx <tpgww@xxxxxxxxxxx> wrote:
> On Wed, 20 Dec 2006 20:53:15 +0100
> "Maarten Maathuis" <madman2003@xxxxxxxxx> wrote:
>
> > I've recently started seeing that no process ever exits as far as
> > emelfm is concerned. Afterwards there is a very high cpu usage.
> >
> > Any idea what could be causing this? (emelfm2-0.3.1)
> No. In 0.3.1 and earlier, command "finishing" is essentially passive, 
triggered by a signal from the operating system and then collecting data from glib.
>
> Is the problem happening for _all_ executed commands?
>
> As it happens, another pre-release is imminent, and it's command execution 
mechanism is completely replaced. That would provide a better platform for 
locating a problem, if it still exists.
>
> Regards
> Tom
>
>
> --
> Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.
>




--
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: