Zombie nodejs processes

After KCL is working long time I see zombie nodejs processes which don't do anything. KCL starts new nodejs processes, but don't kill zombie processes.
Is anybody receive this problem?

Start by reproducing the long-running KCL behavior described in the issue and inspect how its Node.js processes are started and terminated. Done means KCL no longer leaves inactive zombie processes when it starts replacements; the issue does not name specific files or tests, so those must be located during investigation.

Written by the indexing model from the issue text.