did you mean the reply on the Capture Abort thread? This is a different bug, unrelated to that the Capture Abort one. In this case capture doesn't abort, but returns to a different place in buffer than the one it was invoked from.