PuTTY bug portfwd-open-crash

This is a mirror. The primary PuTTY web site can be found here.

Home | Licence | FAQ | Docs | Download | Keys | Links
Mirrors | Updates | Feedback | Changes | Wishlist | Team

summary: Crashes with heavy open/close activity in port-forwarding
class: bug: This is clearly an actual problem we want fixed.
priority: high: This should be fixed in the next release.
present-in: 0.52 2002-06-05 2002-06-06
fixed-in: 2002-06-16 0.53 (0.54) (0.55) (0.56) (0.57) (0.58) (0.59) (0.60)

Apparently, if working in a terminal session at the moment a tunnel is opened, there is a chance of causing a crash (either `Out of memory!', or `Windows has closed PuTTY due to errors').

This tends to be noticeable when lots of port-forwarded connections are being opened and closed (tunnelling HTTP or POP/SMTP for example).

All reports so far that have mentioned the protocol version have been against SSH-2, with local-to-remote tunnelling. There are suggestions that this is correlated specifically with user input rather than just any terminal activity.

Update: We believe this is fixed. I (JTN) can consistently reproduce the problem in 2002-06-05 but not 2002-06-18 (or 2002-08-19).

Audit trail for this bug.


If you want to comment on this web site, see the Feedback page.
(last revision of this bug record was at 2005-03-10 16:36:42 +0000)