PuTTY bug fatal-errors

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

summary: Fatal error handling is patchy and flaky.
class: bug: This is clearly an actual problem we want fixed.
difficulty: tricky: Needs many tuits.
priority: historic: This is an old bug report that we think is either fixed without noticing, or confined to old systems, or too vague.

Fatal error handling is patchy and flaky. It's very easy to throw a fatal error, put up a message box, and then receive a Windows message containing yet more socket data. The MessageBox message loop then dispatches that message automatically and the back end is called reentrantly. Chaos ensues. Solution: the fatal error behaviour should be much more robust. Close all sockets the instant a fatal error occurs; also set some global flags that prevent action messages from having any back end effect.

SGT, 2024-11-17: classifying this bug as historic. This was a note-to-self from the very early days; connection error handling has had a lot of work since then, and it's too vaguely described in any case. Any specific remaining errors should have new bugs raised for them.

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 2024-11-17 14:53:03 +0000)