A 20-year-old bug in Grand Theft Auto: San Andreas, related to how the game handles specific low-level keyboard input, resurfaced in Windows 11 24H2. This bug, originally present in the 2005 release, causes the game to minimize when certain key combinations are pressed, particularly involving the right Windows key. The issue stemmed from DirectInput, a now-deprecated API used for game controllers, and wasn't previously problematic because older versions of Windows handled the spurious messages differently. Windows 11's updated input stack now surfaces these messages to the game, triggering the minimize behavior. A workaround exists by using a third-party DirectInput wrapper or running the game in compatibility mode for Windows 7.
A Reddit post warned Cursor IDE users about a misleading error message claiming their account was locked due to multiple logins. The message, appearing for some users even when they were only logged in on one device, falsely stated that their account was disabled and prompted them to contact support. This erroneous "lockout policy" led to confusion and user cancellations, as people believed they were genuinely blocked from using the IDE. The Cursor team acknowledged the issue, clarifying that no such lockout policy exists and attributing the problem to a bug. They assured users that their accounts were safe and worked to resolve the misleading error.
HN commenters were largely critical of Cursor's handling of the situation. Several pointed out the poor communication, with the "single device" restriction not being clearly conveyed and the error message misleadingly suggesting a lockout due to suspicious activity. Some saw this as a classic example of premature optimization, arguing that preventing multiple logins offered minimal benefit while alienating users. Others speculated about the technical reasons behind the restriction, suggesting it might be related to the complexity of maintaining shared state in Cursor's collaborative features. The overall sentiment was that this incident damaged Cursor's reputation and highlighted a lack of user empathy in their decision-making process.
The Therac-25 simulator recreates the software and hardware interface of the infamous radiation therapy machine, allowing users to experience the sequence of events that led to fatal overdoses. It emulates the PDP-11's operation, including data entry, mode switching, and the machine's response, demonstrating how specific combinations of user input and software flaws could bypass safety checks and activate the high-power electron beam without the necessary x-ray attenuating target. By interacting with the simulator, users can gain a concrete understanding of the race conditions, inadequate software testing, and poor error handling that contributed to the tragic accidents.
HN users discuss the Therac-25 simulator and the broader implications of software in safety-critical systems. Several express how chilling and impactful the simulator is, driving home the real-world consequences of software bugs. Some commenters delve into the technical details of the race condition and flawed design choices that led to the accidents. Others lament the lack of proper software engineering practices at the time and the continuing relevance of these lessons today. The simulator itself is praised as a valuable educational tool for demonstrating the importance of rigorous software development and testing, particularly in life-or-death scenarios. A few users share their own experiences with similar systems and emphasize the need for robust error handling and fail-safes.
Summary of Comments ( 48 )
https://news.ycombinator.com/item?id=43772311
Commenters on Hacker News discuss the GTA San Andreas bug triggered by Windows 11 24H2, mostly focusing on the technical aspects. Several highlight the likely culprit: a change in how Windows handles thread local storage (TLS) callbacks, specifically the order of execution. One compelling comment notes the difficulty in debugging such issues, as the problem might not lie within the game's code itself, but rather in the interaction with the OS, making it hard to pinpoint and fix. Others mention the impressive longevity of the game and express surprise that such a bug could remain hidden for so long, while some jokingly lament the "progress" of Windows updates. A few commenters share their own experiences with similar obscure bugs and the challenges they posed.
The Hacker News post discussing a 20-year-old bug in GTA San Andreas surfacing in Windows 11 24H2 has several comments exploring the technical aspects and implications of the issue.
One commenter highlights the complexity of software interactions, pointing out how a seemingly unrelated change in the operating system can unexpectedly trigger dormant bugs in older applications. They emphasize the difficulty in predicting such issues, especially in large and intricate systems like Windows and a game as complex as GTA San Andreas.
Another comment delves into the specifics of the bug, explaining how the change in Windows 11's handling of specific instructions, particularly related to floating-point operations and denormalized numbers, led to the game's malfunction. This explanation provides a technical understanding of why the bug only surfaced after the Windows update.
Several commenters discuss the challenges faced by developers in maintaining backward compatibility, especially over such long periods. They note that anticipating all possible interactions between a game and future operating system updates is practically impossible. The idea of "bit rot," where software gradually degrades over time due to changes in the surrounding technological environment, is also mentioned.
One commenter mentions a similar experience with another older game, illustrating that this kind of issue isn't unique to GTA San Andreas and highlighting the broader challenge of preserving software functionality across evolving platforms.
There's a discussion about the nature of denormalized numbers and their impact on performance. One commenter questions the practical necessity of handling denormalized numbers in modern hardware and software, suggesting that their support might be more trouble than it's worth in some contexts.
Finally, a few commenters offer potential workarounds for the issue, such as disabling hardware acceleration or using compatibility modes in Windows 11. These suggestions provide practical solutions for users affected by the bug while waiting for a permanent fix.