RunScore 9.0.1 is a major race-day stability patch. We've eliminated the reported mid-race crashes, made the system highly resilient to bad internet and hardware disconnects, and added protections so simple human errors no longer take down your software.
We are incredibly excited to unveil RunScore 9.0.0! A release that marks the beginning of a new chapter. This isn't just an update; it's a complete evolution of the software you've relied on for decades.
This version delivers 188 epics, bug fixes, and major improvements. We have focused on extreme performance, absolute data integrity, and a new community-focused model that makes RunScore accessible to everyone.
We are excited to announce RunScore version 8.4.3. This update focuses heavily on improving stability and reliability while introducing key features to make your race-timing workflow smoother and faster.
You should notice a significant reduction in unexpected crashes, better performance, and several quality-of-life improvements across the application.
RunScore 8.4.2 delivers one of the most comprehensive stability and performance updates in recent history, with 41 tracked improvements addressing long-standing crash scenarios and inconsistencies.
This release strengthens the system's internal architecture, improves crash resistance and file handling, and lays technical groundwork for upcoming feature expansion.
Over the last ten months, our team has focused on a significant issue affecting application stability: memory management. Almost all (96%) of our problems stemmed from insufficient memory management.
With version 8.4.1, we aim for enhanced stability that RunScore has never experienced. We fixed 157 issues spanning memory modernization, runtime validation, entries processing, the Enter screen, and a new results management feature.
The main goal of this release was to improve the program's stability. RunScore 8.4.0 performs runtime checks before operating with memory and will terminate the application if memory corruption is detected, rather than continuing with undefined behaviour.
Starting with this release, RunScore adopts Semantic Versioning 2.0.0. Our team addressed 128 issues to eliminate unpredictable behaviour and outdated code that could cause crashes.
RunScore 8.3.7.5 focuses on stability fixes for Server-Client connectivity, team downloads, chip data processing, and Entries.ini validation, plus improvements for error messages, printer handling, and MyLaps connections.
This release resolves six critical crash scenarios and adds four enhancements for clearer diagnostics and more reliable external timer connectivity.
RunScore 8.3.7.4 resolves critical crashes when viewing results from the Client and when receiving null point-of-read data from external timers.
This release also improves ChronoTrack and MyLaps connectivity with real-time status display, support for up to 50 simultaneous connections, and automatic reconnection within 20 seconds.
RunScore 8.3.7.3 addresses critical stability issues including race-closure crashes, ghost processes in Task Manager, Live Results navigation failures, and listing file exception handling.
This release also adds configuration improvements for events, external timers, ignored chip reads, and the installer package.
RunScore 8.3.7.2 resolves critical crashes during registration processing and duplicate bib handling on the Results screen, and modernizes singleton management and race-folder permission checks.