by "freezes", 'deeter72 almost certainly means that the user interface becomes unresponsive, which is not relevant for servers.
windows has policies that prioritize maintaining user interface and foreground app responsiveness.
windows has policies that prioritize maintaining user interface and foreground app responsiveness.
So? What’s the point here?
you linked a list of all CVEs in macOS. I don't see how this is relevant at all.
tl;dr: I believe you are overblowing the importance of the bugs. In the bigger scheme of things they're more likely inconsequential.
(see my other reply for more)
The first link is a report that the system becomes nonresponsive under memory pressure and a discussion of that report. In that thread, there was not really any agreement about whether this was a bug, let alone what the bug was, or what the fix would be.
The second wasn’t a bug at all, it was a patch proposed set of knobs to allow users to avoid the problem.
Kernel thread for interactive applications in focused window would then have higher priority than background applications improving responsiveness. I am not sure what manipulated the priority, but I assume Xsun (X Window server) did it.
Ok. I got it. Literally speaking there are two (maybe more?) known bugs. Do we know how many are there for Windows and macOS? I get freezes every now and then under macOS, so there _might_ be memory management issues there as well.
My point stills stands because I believe that the bugs you posted are largely inconsequential. Bugs could be very well been patched by now (or not). My guess the fix won't uptick the % of linux in desktop or server market.
IMHO "the truth is in the pudding": if the largest share of mobile OS's is based on linux (android) and largest % in servers in again based on linux, memory management is overall good enough - otherwise the market share would have dropped considerably.
UPDATE: Revisiting the thread question... I'm barking at the wrong tree. The question wasn't about relevance and market %. Your comment is to the point.
Android has had a variety of downstream patches over the last 5-10 years to address this problem. ChromeOS too.