Ask HN: Details behind years old Windows taskbar bug?
There is a long standing bug in Windows, where the hover state on taskbar items - highlight and a window preview - gets stuck after having the computer run for a while, as if the taskbar never notices the cursor leaving it.
I've had this bug on every single Windows version since Windows 7, on every single installation and every single Windows PC I've used actively.
Along the years I've seen people suggest all kinds of workarounds for this, but I've seen none that do more than temporarily fix the issue.
This bug has intrigued me ever since I noticed it being consistent across versions, and most recently I checked if it still applies to Windows 10 Anniversary Update, which it does. Why is it so persistent? Why did it survive the "should-not-call-it-metro" changes to the explorer shell?
Since there's often interesting discussion and insight on obscure bugs in Hacker News, does anyone have any insight on this? Has anyone ever debugged it?
(
21 comments
| 50 points
| on HN
)
However that one in particular iirc has to do with the way input is handled among threads, and how Windows is careful with how activation / focus gets passed among processes.
Since the taskbar needs to do various things without taking input focus or capturing the mouse etc, I would assume the bug has to do with managing this obscure behavior, and missing a notification (or some obscure race condition?) that results in the taskbar not transitioning to the non-hover state.
Outside the taskbar you can often see these bugs in situations such as click, hold the mouse, then move outside of the window or have focus switched. Many times the capturechanged events or activation events do not end up handled properly -- trying to do all this without capturing the mouse or input is even more difficult, though I presume a simple timer would suffice.
Also having read Raymond Chen's "Old New Thing" blog for a while, it's very common that some third party software/extension does something insane with the desktop window and breaks things. It could be something like that. Can you reproduce it on a completely empty fresh install of Windows?
I'm starting to think it may have something to do with the way some people interact with the UI, as some people do not get it at all and some, like me, get it often.
http://superuser.com/questions/61833/windows-7-taskbar-icon-...
One other "bug" I wish they would fix is when you change virtual desktops, the taskbar items reset, apparently, to the order the windows were opened in. Messes me up really bad as I keep the windows in specific order.
As to your question, I figure it's the same as anything else in windows, legacy code. One library gets stacked on top of another, then another, and when the UI pulls from it, it drags up bugs from the entire stack.
You can kill explorer.exe to fix it.
As I am using beefier hardware it gets more difficult to reproduce, but the general pattern is oversaturating I/O: have multiple memory hungry applications swapped out and try to bring them all back.
I usually reboot at that point. This issue has been in Windows since at least Win2000.
[Some peer post says that killing explorer.exe fixes it. I'll try that next time]
I suspect it's one of those very low-priority bugs and thus never gets fixed.
My guess is there some kind of difficult to handle race condition around the states on this type of system UI, particularly for laptops that go in and out of suspend mode.