21–30 of 96 posts
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.
Well then I'll report something about how my PC refuses to stay asleep after I tell it to sleep.
It is funnily interesting to me how they prefer to capitalize the word BUG, perhaps as a means of drawing attention to its (apparent) importance.
The pattern I've seen before is all-caps tags inserted in the code, making for easy grep, e.g. FIXME, BUG, TODO. Perhaps it becomes habit.
Earlier quoted context omitted.
Well then I'll report something about how my PC refuses to stay asleep after I tell it to sleep.
This happens to mine if I have an update pending, worth checking if it's an intermittent issue.
Earlier quoted context omitted.
This issue is on feedback hub for anyone who wants to upvote it: https://aka.ms/Yxum93
Just to highlight supporting bugs from a non-Windows platform... https://s31.postimg.cc/e37910orf/IMG_2425.png
Insightful response in the linked thread: https://sourceforge.net/p/sevenzip/discussion/45797/thread/e...
In 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.
In 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.
Earlier quoted context omitted.
This happens to mine if I have an update pending, worth checking if it's an intermittent issue.
I've dug into it several times. First it was network adapter, which for some reason had a default setting to wake on any received packet (lol, wut?). Then it was waking because there was some setting deep in the system about waking up for scheduled operations. (not scheduled tasks, but timers within individual processes... why???) Now it started again but this time the power management tools report no reason for the…
After adding one, I found out that when the display goes to sleep, Windows sees it as a disconnection, and 'helpfully' wakes up to reorganize all the windows onto one display. That wakes up the Display port monitor, which triggers another reorganization, and the cycle begins again.
Earlier 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.