kdevelop (4.7) launching background *processes*?

[Milian Wolff]

On Wednesday 10 December 2014 15:26:58 René J.V. Bertin wrote:
> On Wednesday December 10 2014 14:57:49 Milian Wolff wrote:
> 
> Hi,
> 
> >> Zombie processes usually indicate that the previous application run
> >> wasn't
> >> terminated cleanly. Can you check whether kdevelop usually exists cleanly
> >> or happens to crash?
> 
> Zombies can also be processes that cannot exit (completely) because they
> cannot close a resource because it's in use by a still running process.
> Yes, kdevelop doesn't leave processes around when it exits, including these
> zombies.
> >QString exe = KStandardDirs::findExe("something");
> >// if it is not found, exe will be empty
> >QProcess p(exe);
> >p.start();
> >
> >On Linux systems, this then produces KDevelop zombies. Maybe we are missing
> >the correct checks in some places. Or maybe it's something else on Mac?
> >Still,
> A check on exe.isEmpty() should suffice, then?
> 
> >you should be able to strace this problem via
> >
> >strace -e process -f kdevelop
> 
> I'll have to figure out what tool has a similar function on OS X, but I'll
> look at Qt's QProcess implementation first. Are you invoking QProcess
> directly, or through your own classes inheriting it?
> 
> The strange thing is that I never noticed this on OS X 10.6.8 ...

QProcess, one way or the other. Sometimes there is the obsolete indirection of 
KProcess in-between, something that we should cleanup in master/KF5.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de