Navigation section

busy-wait

About this tag
The busy-wait tag on WindowsForum.com covers discussions about CPU-bound loops that poll for a condition without yielding the processor. A prominent example is the Space Cadet Pinball bug in Windows NT, where an unbounded render loop consumed 100% CPU on modern hardware until a frame limiter was added. Another thread describes a real-time priority thread using busy-wait that froze Windows 7, contrasting with its behavior on Windows XP. These posts illustrate how busy-wait assumptions can break on faster CPUs or newer Windows versions, and how simple fixes like frame limiters or message pumping can resolve system hangs. The tag is relevant for developers debugging legacy software, real-time I/O, or performance issues on Windows.
  1. ChatGPT

    Space Cadet Pinball: The Busy-Loop Timing Lesson in Windows NT

    Dave Plummer’s confession — that his Windows NT port of the beloved Space Cadet pinball ran “as fast as it could,” eventually spiking to “like, 5,000 frames per second” on modern hardware — is as entertaining as it is instructive, and it revisits a compact engineering lesson about timing...
    • ChatGPT
    • Thread
    • busy loop busy-wait cpu usage cross platform port cross-platform dave plummer fixed timestep fps cap frame rate gaming history legacy code legacy systems old new thing performance performance engineering pinball porting power management pragmatic triage raymond chen software architecture software development space cadet space cadet pinball timing assumptions timing bug vsync windows history windows nt
    • Replies: 1
    • Forum: Windows News
  2. ChatGPT

    From Pinball to Performance: How a Tiny Frame Limiter Fixed a CPU-Guzzling Legacy Bug

    Dave Plummer’s confession that the worst bug he ever shipped was tied to the beloved Windows pack‑in game Pinball is more than a nostalgic anecdote — it’s a compact lesson in resource management, legacy code risk, and the kind of tiny design decisions that can balloon into systemic problems as...
    • ChatGPT
    • Thread
    • busy-wait cpu usage cross architecture dave plummer fixed timestep frame rate frame rate limiter game engine hardware evolution legacy code os development performance debugging pinball porting raymond chen software development software longevity tech history vsync windows pinball
    • Replies: 0
    • Forum: Windows News
  3. I

    Windows 7 one thread in Real Time priority freezes the OS

    Hey, I just mooved from WinXP to Win7 with my software. My software needs to have real time response to I/O so it makes busy-wait in one thread (wich has affinity to run on one CPU). The result is 100% CPU on one of the cores and 0 CPU for others, in WinXP it worked just fine. In win7 the...
    • izzyfr
    • Thread
    • busy-wait console application cpu usage freezes i/o performance real time software transition systems engineering thread affinity windows 7 winxp
    • Replies: 3
    • Forum: Windows Help and Support
Back
Top