luebking added a comment.
This boils down to the question why the process is still lingering around. If the only parent/child link is actually the socket, then it's more likely to zombie around on a bad socket. In this case you can fire as many signals as you want - they'll never be handled (the process isn't interruptable) Otherwise QProcess would setup the child process in a way to die with the parent anyway. If that doesn't happen, the child may have been forked off at some point and in that case lost the deathsig/sigterm connection (according to the prctl manpage, I've actually never tried that myself) tl;dr - somebody needs to test this and ideally check *how* the process refuses to die (but the gdb hassle seems to indicate a zombie) and the process table at this point. REPOSITORY R108 KWin REVISION DETAIL https://phabricator.kde.org/D5589 To: graesslin, #kwin, #plasma Cc: luebking, plasma-devel, kwin, spstarr, progwolff, Zren, lesliezhai, ali-mohamed, hardening, jensreuterberg, abetts, sebas, apol, lukas
