Live data from Hacker News

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

bugzilla.mozilla.org

101–110 of 443 posts

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

#101
post #81
post #3

I would like anyone that considers Microsoft to be a recent champion of Open Source to reflect on corporate doublespeak. It's plausible that this bug was engineered as an attack on Firefox.

Never attribute to malice…

Nowadays a lot of malicious acts are intentionally disguised as stupidity and incompetence. Not necessarily in this case, but that quote really is showing its age.

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

#102
post #44

Earlier quoted context omitted.

Haha, you should enable it with exclusions. It's the best AV out there that isn't an EDR. I disable it in labs but I can't imagine running windows in prod with defender enabled. Don't use windows like it's Linux.

Defender, under certain licenses, is an EDR - https://learn.microsoft.com/en-us/microsoft-365/security/def...

What is an EDR?

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

#104
post #35

> mpengine.dll version 1.1.20200.4 was released on April 4, so the fix should be available for everybody now. See the end of comment 91 to know what version you are using. Also, the latest discoveries in bug 1822650 comment 6 suggest that we can go even further down in CPU usage, with all antivirus software this time, not just Windows Defender. Really nice to see open collaboration between Mozilla and Microsoft devel…

Yes. I mean it took 5 years, but who would count. /s

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

#105

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.

I love calculations like this and hope they are part of every engineer’s line of thinking. I originally came across this thinking in Andy Hertzfeld’s book - https://www.folklore.org/StoryView.py?story=Saving_Lives.txt Performance is time, energy, heat. It’s one of the easiest features to get and there are lots of tools, research, and philosophies to help get it. Memory and storage are similar. For anyone working on l…

It can be a bit dangerous (especially to your employer) to continue that line of thinking, though. How many pieces of software do we collectively work on which would make the world a better place if they didn't exist at all?

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

#106

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.

I love calculations like this and hope they are part of every engineer’s line of thinking. I originally came across this thinking in Andy Hertzfeld’s book - https://www.folklore.org/StoryView.py?story=Saving_Lives.txt Performance is time, energy, heat. It’s one of the easiest features to get and there are lots of tools, research, and philosophies to help get it. Memory and storage are similar. For anyone working on l…

How did the idea of avoiding premature optimization get misapplied to client-side apps where the entity writing the software is not the one paying for electricity, cooling, and people's time when the software takes much longer to run than it could? When did a lot of software devs stop caring?

Pardon me, I think there are some electron devs at my door asking for a word. They might have baseball bats.

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

#107
post #89

Earlier quoted context omitted.

Continuous. We need one less coal plant to support the Firefox code after the bug fix.

Coal makes only 12% of the electricity, in the US at least. Natural gas makes 36% and oil makes 33%. https://www.eia.gov/energyexplained/us-energy-facts/

What does that have to do with anything? "Coal plant" is being used as a unit of power here.

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

#108

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.

Would be interesting to see the energy usage of Windows Update computed in a similar way.

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

#109

Earlier quoted context omitted.

Defender, under certain licenses, is an EDR - https://learn.microsoft.com/en-us/microsoft-365/security/def...

What is an EDR?

endpoint detection and response: https://learn.microsoft.com/en-us/microsoft-365/security/def...

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

#110

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

If you use Windows Pro and Enterprise, you can use GPO to disable Defender. Just run gpedit.msc and edit a few of the policies to disable real-time protection etc.

Under Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus

  - Turn off Microsoft Defender Antivirus -> set to Enabled
Under Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Real-Time Protection

  - Turn on behavior monitoring -> set to Disabled
  - Monitor file and program activity on your computer -> set to Disabled
  - Turn on process scanning whenever real-time protection -> set to Disabled
  - Turn on behavior monitoring  -> set to Disabled
Restart the computer and Real-time protection should be disabled permanently (until you reverse the same settings through gpedit.msc at least).
Post reply on HN