Windows 10 Bug Leaves Google Engineer's 24-Core System Can not Just Move The Mouse

Imagine rocking a system with a 24-core processor that supports Hyper Threading, 64GB of RAM, and a fast solid state drive. Pretty line setup, right? The last thing you would expect is that performance would be a problem, but for an engineer who owned such a configuration, it was not enough to prevent the mouse from developing a hitch and sometimes even freezing in seconds at a time. In fact, such a burly CPU might actually exacerbate the problem. How is that like that?

The actual guilt is Windows 10 and specifically a "serious process destruction performance error" in the operating system detected by a programmer working for Google . In a long blog post, Bruce Dawson outlines the steps he took to track what led to the mouse stabbing and stopping.

Dawson would notice hitch in his mouse when he built Chrome . While stackers and hardware hangers can be expected (to a degree) when CPU utilization is 100 percent, Dawson says that CPU usage rarely jumped over the 50 percent threshold. There was obviously something else for play so he whipped out some troubleshooting tools and started performing performance tracks on Windows 10.

Skip what appeared to be a rabbit hole initially led him to a Windows function called NtGdiCloseProcess, which Is responsible for exciting processes.

"Process creation is CPU-bound as it should be. Process interruption, but CPU is bound at the beginning and end, but there is a long period in the middle (about one second) Where it is serialized using blot One of the eight hypertrokes on the system, as 1,000 processes are fighting over a single lock inside the NtGdiCloseProcess. This is a serious problem. This period represents a time when programs will hang and mouse movements will hitch- and sometimes this serial period is several seconds Longer, "explains Dawson.

This is not something that the average user is likely to come across. But it can be an annoying problem for programmers who work with many processes, as was Dawson's case. Chrome is a rather large application that involves destroying many processors in quick succession. And because of the way this error works, the more cores and threads in a system, the worse this side effect can be.

Dawson says this is not a problem in Windows 7 . It's not a good thing for Microsoft as it tries its best to get as many as possible upgrade to Windows 10 . Dawson has reported the error to Microsoft, and it is currently investigating the case.

) insertAfter (jQuery (. & # 39; # Initdisqus & # 39;));
LoadDisqus (jQuery (& # 39; # initdisqus & # 39;), disqus_identifier, url);

Otherwise {
SetTimeout (function () {disqusDefer ();}, 50);

DisqusDefer ();

Function loadDisqus (source, identifier, url) {

If (jQuery ("# ​​disqus_thread"). Length) {
JQuery ("# ​​disqus_thread") remove (.);
. JQuery (& # 39;

& # 39;) insertAfter (source);

If (window.DISQUS) {

DISQUS.reset ({
Reload: true,
Config: function () { = identifier; = url;

} Otherwise {

// Insert a wrapper into HTML after the relevant "View Comments" link

Disqus_identifier = identifier; // Set the identification argument
Disqus_url = url; // Set the permalink argument

// add disqus embed script to html
Var dsq = document.createElement (& # 39; script & # 39;); Dsq.type = & # 39; text / javascript & # 39 ;; Dsq.async = true;
Dsq.src = & # 39; https: // & # 39; + Disqus_shortname + & # 39; & # 39 ;;
JQuery (& # 39; main & # 39;) append (DSQ) .;


JQuery (& # 39; show-disqus.) Shows (.);
Source.hide ();

Function disqusEvent ()
IdleTime = 0;

Source link