Earlier quoted context omitted.
> I don't think it's the FireFox' team's responsibility to be aware of and take into account arbitrary software intercepting system calls. Per the bug report, Firefox was generating up to ~14,000 calls where Chrome was generating ~300, though. Surely it is Firefox' team's responsibility to use system calls in a sane way, say not almost 50x more than the competition?
Did you read the bug report? This is literally about writing to files in a temp folder. Surely you can optimize that but you should also be able to assume that this does not use excessive amounts of CPU on a modern operating system.
Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
41–50 of 443 posts
Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#42I 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.
Do we have to assume negative intent every time something like this happens?
Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#43Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#44My only interaction with Windows Defender is the (undefeatable) nag popup every boot that warns me it is disabled.
Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#45Quick 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.
Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#46Quick 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.
Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#47Quick 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.
Who knows what edge case triggered that bug to manifest but I for one haven't seen it in the wild in the years we've been using FF.
Probably difficult in such a large org to allocate dev resources to chase down and fix a bug few people were impacted by.
Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#48Earlier quoted context omitted.
Have you any semblance of proof of this? By the looks of it took Firefox a few years to figure out what the repro was, they reported it to MS, it was (very) promptly fixed and they were warned that the syscall they were using isn't being used as intended and they should consider changes to FF for future use cases.
I've lived through the browser wars and I can tell you that this would not surprise me one bit.
Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#49Quick 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.
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.
Re: Microsoft fixes 5-year-old Defender bug, reducing Firefox-related CPU use by 75%
#50Quick 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.