![]() ![]() They came to the conclusion that the calls to VirtualProtect were abnormally high, which in turn caused the performance issue. Mozilla's engineers worked with Microsoft's team to solve the problem. Essentially, it was generating way too many ETW events than normal, and was using 5 times more CPU power to do this with Firefox as compared with Chrome and other browsers.įurther investigations shed light on the root cause, Windows Defender's real-time protection was invoking VirtualProtect several times. it was processing ETW (Event Tracing for Windows) from other processes. They discovered that the executable was accessing sechost.dll to run ProcessTrace, i.e. Mozilla's engineers narrowed down the issue to the Antimalware Service Executable, which is Msmpeng.exe (Microsoft Malware Protection Engine). That means it was not restricted to Windows 11, it also affected Windows 10. The issue had been reported on Bugzilla 5 years ago (May 2018). Some people had compared the performance with other browsers such as Chrome and Edge, and found that it didn't affect them, the bug was limited to Firefox. Many users said that the performance was so bad that their PCs would lag when using the browser. When Firefox was running, Windows Defender's Antimalware Service Executable would act up, causing its CPU Usage to rise significantly. ![]() ADVERTISEMENT Windows Defender bug was causing high CPU usage in Firefox
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |