Hacker News Reader

Comment by dgellow | Hacker News Reader

> 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 development teams resulting in a net improvement for everybody.

View on HN

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

People care about open Firefox bugs much older than that. Basically any long-lived program will have ancient bugs that never made it onto someone’s todo list.

For example, it only took 20 years (!!) to stop Ctrl+Q from quitting Firefox on Linux. :)

IIRC, a couple of patches did get submitted, but never accepted for unknown reasons.

Isn't Ctrl-Q quitting the program normal and expected behavior? For example, right now on Firefox 111, I can see in the File menu that the "Quit" option has the keyboard shortcut Ctrl-Q. I'm fairly sure it works.

On linux, I'd want it to be dictated by my DE or WM. I have Super+shift+q set to close windows on my machine, so I wouldn't be crazy about software adding its own keybind to do the same.

It is a very common binding.

Thank you, I was wondering why it stopped working, but never took the time to investigate... :D

Well, a net improvement for the people who paid Microsoft for an OS that wasted their energy and wore down their computer (heat damage) for 5 years.

I'll note that mpengine.dll was updated for me on Windows 11 Pro 21H2 in spite of my blocking autoupdates via Group Policy.

To be clear: I'm aware Windows Defender updates itself independently of Windows Update, and I actually don't mind and even appreciate this behaviour since Defender updates almost always aren't intrusive unlike the rest of Windows Update.

Just an FYI for people with similar configs.

This update is causing intermittent browsing issues in Firefox and Chrome for me and several others (not Edge, though). Getting 'PR_END_OF_FILE_ERROR' in Firefox, with Chrome experience issues at the same time (though Chrome does eventually load the page)

Reply on news.ycombinator.com