Defunct ssh processes (connection problems)

[Alexander Taler]

I'm working with the current trunk version of bzr-eclipse.

I quite often get defunct (zombie) ssh processes resulting from bzr-eclipse ssh connections, like this:

 5868 ? Sl 1:03 \_ /usr/lib/jvm/java-7-openjdk-amd64/bin/java -Dosgi.requiredJavaVersion=1.5 -Dhelp.lucene.tokenizer=standard -XX:MaxPermSize=256m -Xms40m -Xmx512m -Declipse.pde.launch=true -Dfile.encoding=ANSI_X3.4-1968 -classpath /home/dissent/opt/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar org.eclipse.equinox.launcher.Main -launcher /home/dissent/opt/eclipse/eclipse -name Eclipse -showsplash 600 -product org.eclipse.platform.ide -data /home/dissent/prj/idereal/dev/bzr-eclipse/dev/1.2-stab/runtime-EclipseApplication -configuration file:/home/dissent/prj/idereal/dev/bzr-eclipse/dev/1.2-stab/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/ -dev file:/home/dissent/prj/idereal/dev/bzr-eclipse/dev/1.2-stab/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/dev.properties -os linux -ws gtk -arch x86_64 -nl en_US -consoleLog
 7002 ? Sl 0:00 \_ /usr/bin/python /usr/bin/bzr start-xmlrpc
 7074 ? Z 0:00 \_ [ssh] <defunct>
 7085 ? Z 0:00 \_ [ssh] <defunct>

I believe this may cause ssh connection problems, e.g. failure to branch from launchpad. Which is why I have ranked the issue high.

This happened most recently when I cancelled a project checkout attempt, and I believe I've seen it before in connection to trying to checkout several projects in a row.

[Piotr Piastucki (piastucki)]

I think this is actually an issue in bzr-xmloutput rather than in bzr-eclipse, please also see https://bugs.launchpad.net/bzr-xmloutput/+bug/516537.

[Alexander Taler (alex-idereal)]

I think it's actually a problem with bazaar itself, not handling sub processes correctly. Here are some bzr bugs which may be related:

Bug #141172
Bug #1018477

[Alexander Taler (alex-idereal)]

I have investigated further and reported a bug against Bazaar. Bug #1189051

This doesn't appear to be a cause of connection problems, so I am closing this bug.