PuTTY semi-bug hard-hangs

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 · Snapshot | Docs | Changes | Wishlist

summary: PuTTY becomes unresponsive / unkillable on Win2000/XP
class: semi-bug: This might or might not be a bug, depending on your precise definition of what a bug is.
difficulty: taxing: Needs external things we don't have (standards, users etc)
present-in: 0.52 2002-02-24 0.53b 0.54
fixed-in: 2004-03-18 c4bfa9b7b77f719a61de6049c9c18d80c9685c9b (0.55)

Apparently, for some people, PuTTY randomly becomes unresponsive with Win2000/XP.

We've been getting rare but persistent reports of this for a while, but there seems to have been a rash of them recently (Feb 2004). None of us have ever seen this, so we're going to need some help if we're to stop it happening.

Common characteristics of the reports we've had:

If I had to make a guess, I'd investigate some of the trickery we use to get noise for random numbers. My notes also suggest that I thought someone thought that sound might be implicated, but I can't find any evidence for that now.

Once the system has got into this state, an SSH packet log of a new session which hangs might be useful, so we can infer exactly where it's hanging and what it might be doing (since there's been a suggestion that it's some way into the SSH protocol).

If someone can debug one of the hanging PuTTY processes and tell us where it's got stuck, that would be good too.
Update, 2004-03-17: someone did this, and PuTTY is hanging in noise_get_light(), around the call to GetSystemPowerStatus().


Update, 2004-03-17: one of our correspondents has been trying a version of the development code (more or less equivalent to 0.54) with the GetSystemPowerStatus() call disabled, and has reported that the problem seems to have gone away.

This source of noise has now been removed as of 2004-03-18 (there were other good reasons too). Please let us know if this appears to solve (or not!) the problem.

(Perhaps we've been getting more reports recently because modern BIOI / Windows versions / whatever are more upset by frequent calls to the APM BIOS or whatever it is than older systems?)

If you want to comment on this web site, see the Feedback page.
Audit trail for this semi-bug.
(last revision of this bug record was at 2017-04-28 16:52:45 +0100)