Thread replies: 6
Thread images: 1
Thread images: 1
Anonymous
Windows 10 BTFO again 2017-07-12 02:14:28 Post No. 61329600
[Report] Image search: [Google]
Windows 10 BTFO again 2017-07-12 02:14:28 Post No. 61329600
[Report] Image search: [Google]
File: image6[1].png (18KB, 629x301px) Image search:
[Google]
![image6[1].png](https://i.imgur.com/XhgHI9m.png "image6[1]")
18KB, 629x301px
https://randomascii.wordpress.com/2017/07/09/24-core-cpu-and-i-cant-move-my-mouse/
>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.
>this serialization on process shutdown is a new issue, introduced sometime between Windows 7 and Windows 10.
This is what happens when you hire people who can't even poo in the loo to write your operating system
>>
Probably just needs to update his drivers
>>
>>61329600
I take bait for 200$
>>
honestly this is nothing
this is just a bug
some of the stuff microsoft does on PURPOSE is truly shocking
>>
>>61329600
Pro tip: 48-core servers are pretty new. NT kernel's schedulers were written when even 2-core set-up was extremely rare. Chrome build system, due to its own weird quirks, hit some edge cases Microsoft didn't have in their test suites.
>>
>>61329724
This. I read this article 2 days ago and thought the bug must've been pretty obscure to be around this long and is probably not really a big deal.
Thread posts: 6
Thread images: 1
Thread images: 1