R3 | Delphi 2017

Worse, the much-hyped Linux compiler (DMSC) had a memory leak in TThreadPool so severe that server applications crashed every 48 hours.

Officially, there was no “R3.” The official release cadence gave us 10.2 Tokyo in March 2017, followed by a series of “hotfixes” and point releases (10.2.1, 10.2.2, 10.2.3). But internally — and in the hearts of a small, devoted community — became known as R3. The State of Emergency By autumn 2017, Delphi developers were facing a perfect storm. Windows 10 Fall Creators Update had just rolled out, breaking VCL manifest handling for older apps. The iOS 11 compiler chain had shifted, leaving FireMonkey mobile apps unable to submit to the App Store. And the new TEdit control on Android had a nasty habit of swallowing keyboard inputs on Samsung devices. delphi 2017 r3

On December 27, 2017, a user named “Alister” posted on the Embarcadero forums a link to a 347 MB ZIP file named Delphi2017_R3_hotfix_pack.7z . The thread title: “If you need stability before Rio, try this.” Worse, the much-hyped Linux compiler (DMSC) had a

Embarcadero’s main team was already deep in the architecture for 10.3 Rio (codenamed “Carnival”). The official word was: “Hotfixes will arrive in Q1 2018.” Legend says a small, unofficial task force inside the R&D team — two senior engineers in Australia and one in the Czech Republic — decided to break the rules. Working over Christmas shutdown, they cherry-picked critical fixes from the Rio branch and backported them to the 10.2 Tokyo codebase. The State of Emergency By autumn 2017, Delphi