classicmenu-indicator leaks 'sh' zombie processes ; a 2-fold bug.

Bug #1456574 reported by Valentin Quequet on 2015-05-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ClassicMenu Indicator
Undecided
Unassigned
classicmenu-indicator (Ubuntu)
Undecided
Unassigned

Bug Description

1st part of this 2-fold bug:

There is one 'sh' process created each time classicmenu-indicator launches a program.

Unfortunately, such 'sh' processes do wait for the application just launched to finish.

Because 'sh' is invoked the following way :

    /bin/sh -c sgt-dominosa # example while running one of my favourite games

this 'sh' process is kept living until I quit the 'sgt-dominosa' app/game (a good one).

This 'sh' process would vanish (ideally, if garbage collected, see 2nd part below) if told to launch the app in the background.

But in the current implementation, this 'sh' process just keeps straying around like a lazy dog, consuming resources (memory, not cpu).

2nd part of this 2-fold bug:

classicmenu-indicator does not do wait(2)/waitpid(2) the right time : if you launch (many) a number N of apps or instances of app, and you close them all, then you will have N such 'sh' zombie processes straying around. The only way to get rid of them is to ask classicmenu-indicator to launch an app again. So, in the end, you will always have many or at least one 'sh' processe(s) either waiting for apps to terminate, or in a zombie condition.

Hope this helps.

Regards,
Valentin

Graham Inggs (ginggs) on 2015-05-20
Changed in classicmenu-indicator (Ubuntu):
status: New → Confirmed
Graham Inggs (ginggs) wrote :

This was fixed in upstream version 0.08.

Changed in classicmenu-indicator:
status: New → Fix Released
Graham Inggs (ginggs) wrote :

Patch cherry-picked from upstream.

tags: added: patch
Graham Inggs (ginggs) wrote :

Patch needed to fix a FTBFS on recent Ubuntu releases.
Cherry-picked from Distribute 0.6.49

Graham Inggs (ginggs) wrote :

@Valentin: Please try classicmenu-indicator from my PPA:
https://launchpad.net/~ginggs/+archive/ubuntu/testing

Thanks for the quick answer.

Moreover, your patch gio.appinfo.launch.patch works just fine here.

Good Job !

Sincerely,
Valentin

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package classicmenu-indicator - 0.07-0ubuntu2

---------------
classicmenu-indicator (0.07-0ubuntu2) wily; urgency=medium

  * Use gio.appinfo.launch() to start programs (LP: #1456574).
  * Use python-setuptools instead of distribute_setup.py.
    (fixes FTBFS in recent Ubuntu releases)

 -- Graham Inggs <email address hidden> Mon, 08 Jun 2015 19:32:06 +0200

Changed in classicmenu-indicator (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers