Live data from Hacker News

Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

bugzilla.mozilla.org

51–60 of 443 posts

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#51
post #43
post #16

Earlier quoted context omitted.

You'd think they'd target Chrome (>60% market share on Desktop) rather than Firefox with < 8% market share.

The new Edge browser is basically a revamped Chromium, so that'd be a pretty dumb move.

Seems less dumb than targeting Firefox though. Presumably, in the universe of this conspiracy hypothesis, they would do it in a way that wouldn't effect Edge.

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#52

Quick napkin math of the wasted power : Firefox has ~300e6 users, let's assume the bug wasted 5 extra watts 4 hours a day. That's 250 megawatts saved, the equivalent of an average coal power plant. Because some Microsoft engineer missed a bug.

The units don't make sense. You might mean megawatt-hours?

It was not so well explained, but the GP does mean averaged over 24 hours, the power requirement is 250MW.

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#53

Earlier quoted context omitted.

doesn't this bug only manifest itself if one is using microsoft defender as their only security solution, and not a 3rd party AV/IS? if so, then the number of Firefox users in this calculation is much lower.

I don't know if that's the case. I'm a Firefox user but consider all the 3rd party apps nearly as much malware as the things they are trying to solve. I run strictly defender and try to make good choices when downloading and browsing.

well, if we're taking strictly subjective personal experiences as some sort of a relevant benchmark, then I'm a Windows Firefox user that has never used MS defender for any length of time, and always strictly a reliable low-impact 3rd party AV like ESET or Emsisoft. so I guess the two of us cancel each other out.

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#54

Quick napkin math of the wasted power : Firefox has ~300e6 users, let's assume the bug wasted 5 extra watts 4 hours a day. That's 250 megawatts saved, the equivalent of an average coal power plant. Because some Microsoft engineer missed a bug.

The units don't make sense. You might mean megawatt-hours?

No typo, I meant Watts. I averaged the 4 hours per day

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#55

Quick napkin math of the wasted power : Firefox has ~300e6 users, let's assume the bug wasted 5 extra watts 4 hours a day. That's 250 megawatts saved, the equivalent of an average coal power plant. Because some Microsoft engineer missed a bug.

> the equivalent of an average coal power plant

Produces in an hour, four hours?

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#56

Quick napkin math of the wasted power : Firefox has ~300e6 users, let's assume the bug wasted 5 extra watts 4 hours a day. That's 250 megawatts saved, the equivalent of an average coal power plant. Because some Microsoft engineer missed a bug.

The units don't make sense. You might mean megawatt-hours?

No, it makes sense. The parent is talking about continuous power measured in megawatts, i.e. megawatt-hours per hour, or megawatt-days per day.

300 million users * 4 hours/day * 5 watts = an average continuous savings of 250 MW.

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#57

Quick napkin math of the wasted power : Firefox has ~300e6 users, let's assume the bug wasted 5 extra watts 4 hours a day. That's 250 megawatts saved, the equivalent of an average coal power plant. Because some Microsoft engineer missed a bug.

The units don't make sense. You might mean megawatt-hours?

one way it could just be mW is if he/she meant “a coal power plant for the 5 years that the bug was active”

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#58

My only interaction with Windows Defender is the (undefeatable) nag popup every boot that warns me it is disabled.

My car also nags me every time I unbuckle my seatbelt to park yet that doesn't mean everyone should have it unbuckled all the time. There's a reason it's designed to be naggy.

Having everyone easily disable Windows Defender will not lead to a great outcome.

There's a reason malware on Windows has been on a steep decline from the Windows XP days and I'd prefer it to keep it that way.

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#59

What apps other than Firefox might this have affected that badly (75% CPU usage)?

I had an issue in early builds of W11 with use of WSL 2 & Node, Github and VS Code. Something in the git change detection process caused Defender to decide it just decided it wanted 100% of a single thread on the 5600X system I was using. While coding it would just have a core screaming at well over 4Ghz. Just all of Mankind's greatest innovations that lead to 7nm lithography and incredible processor design just to be a space heater. I never did get it figured out at the time. It also re-enables itself. So that's cool.

Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%

#60

Earlier quoted context omitted.

The units don't make sense. You might mean megawatt-hours?

No, it makes sense. The parent is talking about continuous power measured in megawatts, i.e. megawatt-hours per hour, or megawatt-days per day. 300 million users * 4 hours/day * 5 watts = an average continuous savings of 250 MW.

Ok, I get it now. This does make sense.
Post reply on HN