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

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