5 ms·
On Windows 11 24H2, more stack space was modified by a new implementation of Critical Sections. IMHO this shows the downfall of Microsoft. Why did they do that
by userbinator 2y ago
On Windows 11 24H2, more stack space was modified by a new implementation of Critical Sections.
IMHO this shows the downfall of Microsoft. Why did they do that? Critical sections have been there for many decades and should be basically bug-free by now. My best guess is someone thought they'd "improve" things and rewrote it, then made some microbenchmark that maybe showed the dubious improvement.
The other comment here mentions Raymond Chen, who wrote this article about why backwards-compatibility is very important (and arguably what got Microsoft into the position it's in today):
https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41363 https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41...
and also this memorable case: https://news.ycombinator.com/item?id=2281932 https://news.ycombinator.com/item?id=2281932
- kittoes 2y agoReally? Someone depending on UB in their software represents the downfall of Microsoft?! What a hot take...
- devnullbrain 2y agoUser has working software. User updates operating system. User has broken software. That's a problem for the party trying to sell operating system updates.
- voidspark 2y agoThe software was fundamentally broken before the OS update. It was working by pure random chance with undefined behaviour. It’s a C++ issue, not an OS issue. The same code compiled for another OS would have different random results.
- Uvix 2y agoWhile this is technically correct that doesn’t get the customer to put the blame where it belongs.
- smallstepforman 2y agoNot a C++ issue, but a sloppy developer issue.
- userbinator 2y agoThe problem is hostile pedants who neglect to consider the human element.
- voidspark 2y agoThis is an existing bug in GTA, not Windows 11.