PuTTY bug portfwd-open-crash

This is a mirror. Follow this link to find the primary PuTTY web site.

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Pre-release · Snapshot | Docs | Privacy | Changes | Wishlist

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 3f8d151c5a26fec09708b2a51b57aabf3d7bd38f 0.53

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).

If you want to comment on this web site, see the Feedback page.
Audit trail for this bug.
(last revision of this bug record was at 2016-12-27 11:40:22 +0000)