So this morning I got an unexpected clue as to what might be causing this: I had an ssh process connected to bazaar.launchpad.net from yesterday -- and its parent was the bzr-notify process. Now, this may be bug #335180, or just the fact that bzr-notify doesn't run the cycle collector very often, but if this affects more than 25% of Canonical employees even, it could be responsible for a large enough number of apparently stale processes on the server.
I've just sent off to ec2test a change that will disconnect connections that are idle (no traffic in either direction) for more than an hour, which will hopefully kill the problem off once and for all.
So this morning I got an unexpected clue as to what might be causing this: I had an ssh process connected to bazaar. launchpad. net from yesterday -- and its parent was the bzr-notify process. Now, this may be bug #335180, or just the fact that bzr-notify doesn't run the cycle collector very often, but if this affects more than 25% of Canonical employees even, it could be responsible for a large enough number of apparently stale processes on the server.
I've just sent off to ec2test a change that will disconnect connections that are idle (no traffic in either direction) for more than an hour, which will hopefully kill the problem off once and for all.