Earlier quoted context omitted.
As a Microsoft employee, I can say that that feedback is taken pretty seriously in most teams, especially if the description is good or if the problem recorder/screenshot tool is used. It's not all based on up votes.
Hmm...excited to hear that I can stop devoting time to figuring out why my wife's laptop constantly runs its fan due to service processes that constantly burn CPU!
Windows 10 works incorrectly with Large memory pages
51–60 of 96 posts
Re: Windows 10 works incorrectly with Large memory pages
#52Earlier quoted context omitted.
Rather unconventional, but Windows 10 on desktop and mobile do have a Feedback Hub [1] where Windows 10 users are able to provide all sorts of feedback, either as a suggestion or a problem . All the feedbacks are public and users can freely vote them up to draw more attention on them. The more vote they have, the more likely they receive a response from the developers and also get the priority in the queue of issues…
As a Microsoft employee, I can say that that feedback is taken pretty seriously in most teams, especially if the description is good or if the problem recorder/screenshot tool is used. It's not all based on up votes.
Re: Windows 10 works incorrectly with Large memory pages
#53Earlier quoted context omitted.
On the other end of that spectrum, it seems MS have had large teams of QA people doing proactive outreach for security problems. My family members have been contacted 6 times in the past 2 years, each time to let them know that MS had detected a security problem and they needed to help us install a patch immediately.
How would you distinguish between MS personnel and scammers calling your house to have you install malware?
Re: Windows 10 works incorrectly with Large memory pages
#54Earlier quoted context omitted.
The Feedback Hub app in Windows 10 is how someone can publicly submit and comment on public issues and suggestions relating to Windows (and various other Microsoft-related/provided components).
This issue is on feedback hub for anyone who wants to upvote it: https://aka.ms/Yxum93
Re: Windows 10 works incorrectly with Large memory pages
#55For all the improvements to Windows that have come from Microsoft thanks Nadella & co., it is still rather shocking to realize Windows has no public bug tracker, and no real way to report these issues besides screaming loudly and hoping someone in Redmond hears you. It's even worse customer service than Google, which is quite an achievement.
Re: Windows 10 works incorrectly with Large memory pages
#56Earlier quoted context omitted.
Just to highlight supporting bugs from a non-Windows platform... https://s31.postimg.cc/e37910orf/IMG_2425.png
Not only do you have to be on Windows 10 (Anniversary Update or newer), you have to be signed into a Microsoft account in the Feedback Hub to even view anything.
Re: Windows 10 works incorrectly with Large memory pages
#57For all the improvements to Windows that have come from Microsoft thanks Nadella & co., it is still rather shocking to realize Windows has no public bug tracker, and no real way to report these issues besides screaming loudly and hoping someone in Redmond hears you. It's even worse customer service than Google, which is quite an achievement.
The googleproductforum.com (whatever it's called) which is usually the #1 result in Google is absolutely worthless.
I am not joking. It is infuriatingly worthless.
Re: Windows 10 works incorrectly with Large memory pages
#58Earlier quoted context omitted.
Heh, yeah, I'm not buying it. How long has the "Windows 10 Start Menu stopped working" bug been around now? And the most consistent fix is still to just do an in-place reinstall?
Yep. This shoots me in the face at least once a week. Also two other problems: 1. The start menu latency is now so bad you have to forcibly wait 2-3 seconds before typing your search after hitting the start button. This is on a stacked E5 Xeon workstation class machine. 2. Search is crap. I can type "visual" and visual studio doesn't come up!?!?
Re: Windows 10 works incorrectly with Large memory pages
#59In reading the article it's clear this is not a bug, it's API abuse. The documentation for VirtualAlloc is very clear that Large Pages should be a one time allocation thing are not intended for general malloc replacement.
Api abuse should not lead to system crashes or global memory corruption.