kdevelop (4.7) launching background *processes*?

[Kevin Funk]

On Wednesday 10 December 2014 12:36:33 René J.V. Bertin wrote:
> Hi,
> 
> I just noticed this:
> 
> #> ps -axlww | fgrep kdevelop
>   505 16877 81395     408e   0  46  0  5605220 695028 -      U              
>     0 ttys000    8:25.50 kdevelop --ps 505 17231 16877     2006   0   0  0 
>       0      0 -      Z                   0 ttys000    0:00.00
> (kdevelop.bin) 505 17232 16877     2006   0   0  0        0      0 -      Z
>                   0 ttys000    0:00.00 (kdevelop.bin) 505 17233 16877    
> 2006   0   0  0        0      0 -      Z                   0 ttys000   
> 0:00.00 (kdevelop.bin) 505 17377 16877     2006   0   0  0        0      0
> -      Z                   0 ttys000    0:00.00 (kdevelop.bin) 505 17378
> 16877     2006   0   0  0        0      0 -      Z                   0
> ttys000    0:00.00 (kdevelop.bin) 505 17379 16877     2006   0   0  0      
>  0      0 -      Z                   0 ttys000    0:00.00 (kdevelop.bin)
> 505 17380 16877     2006   0   0  0        0      0 -      Z               
>    0 ttys000    0:00.00 (kdevelop.bin)
> 
> This is on OS X, and the kdevelop entry in my path is actually a symlink to
> kdevelop.bin, so those zombies are real processes, not some kind of threads
> as Linux apparently tends to do sometimes.
> 
> Does KDevelop indeed launch background processes (and where), or is this
> some kind of anomaly?

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?

Maybe try to run kdevelop in the debugger to catch those crash on exits.

Greets

-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org