zlacker

[return to "Firefox engineers discover a Windows Defender bug that causes high CPU usage"]
1. mconle+h3[view] [source] 2023-04-05 19:04:46
>>mconle+(OP)
TL;DR: Windows Defender had a bug that made certain system calls expensive on CPU cycles when Defender's Real-time Protection feature is enabled. After discovery, Mozilla reported this issue to Microsoft. Microsoft is releasing a patch that should result in lower CPU usage when using Firefox on sites like YouTube (a ~75% CPU usage reduction was noted when browsing YouTube in Firefox with the fixed version of Defender).

It seems like the HN submission form truncated the # from the end of the URL I linked to, which linked to the relevant comment. I'll try that here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1441918#c82

and

https://bugzilla.mozilla.org/show_bug.cgi?id=1441918#c91

◧◩
2. nikanj+xH1[view] [source] 2023-04-06 07:17:49
>>mconle+h3
The biggest surprise for me was Microsoft actually fixing it.
◧◩◪
3. elygre+EM1[view] [source] 2023-04-06 08:02:46
>>nikanj+xH1
Is that because you don't expect programmers in general to fix their bugs? Or do you think Microsoft in particular don't care about their products?
◧◩◪◨
4. nikanj+XP1[view] [source] 2023-04-06 08:35:45
>>elygre+EM1
Because once a corporation grows larger than some singularity threshold, there seems to be a bug event horizon where all bug reports just disappear.

Send a bug report to a five-person software company, their lead dev contacts you the same day and has a patched version ready to go in a week. Send a bug report to Microsoft / Citrix / Apple / etc, and you'll never hear back.

[go to top]