Linked by Thom Holwerda on Mon 10th Jul 2017 18:27 UTC
Windows

This story begins, as they so often do, when I noticed that my machine was behaving poorly. My Windows 10 work machine has 24 cores (48 hyper-threads) and they were 50% idle. It has 64 GB of RAM and that was less than half used. It has a fast SSD that was mostly idle. And yet, as I moved the mouse around it kept hitching - sometimes locking up for seconds at a time.

So I did what I always do - I grabbed an ETW trace and analyzed it. The result was the discovery of a serious process-destruction performance bug in Windows 10.

Great story.

Permalink for comment 646546
To read all comments associated with this story, please click here.
RE: just terrible...
by FlyingJester on Mon 10th Jul 2017 19:37 UTC in reply to "just terrible..."
FlyingJester
Member since:
2016-05-11

Or you could say that Chrome's poor thread safety, requiring separate processes, and lack of proper memory management in a 'burn the process and let the OS figure it out' has drawbacks.

Reply Parent Score: 1