A computer glitch brought F1’s Malaysia race to a halt.
First, it was a rainstorm. Then the cars couldn’t accelerate properly. Then everyone had to wait around for a software update. That’s how a race at the Sepang International Circuit ended up starting 90 minutes late. The new engines have proven controversial and drawn plenty of ire from drivers. > After being idle on the throttle and letting the car slow, as is the norm on a formation lap, the software bug prevented the electrical power from kicking in. Tombazis described it as being a “loop.” The computer was stuck and unable to initiate a power return. For some drivers, the only solution was to stop and reset the car to get it going again. Esteban Ocon compared it to restarting Windows on a computer. [Link: How computer software bugs led to F1’s Malaysia farce: ‘Totally unacceptable’ | https://www.nytimes.com/athletic/7658750/2026/10/04/bahrain-grand-prix-software-bugs-explainer/ | The Athletic]
First, it was a rainstorm. Then the cars couldn’t accelerate properly. Then everyone had to wait around for a software update. That’s how a race at the Sepang International Circuit ended up starting 90 minutes late. The new engines have proven controversial and drawn plenty of ire from drivers. > After being idle on the throttle and letting the car slow, as is the norm on a formation lap, the software bug prevented the electrical power from kicking in. Tombazis described it as being a “loop.” The computer was stuck and unable to initiate a power return. For some drivers, the only solution was to stop and reset the car to get it going again. Esteban Ocon compared it to restarting Windows on a computer. [Link: How computer software bugs led to F1’s Malaysia farce: ‘Totally unacceptable’ | | The Athletic]
Topics in this story
Gathered from external sources. Rights to this text belong to whoever originally published it.