![]() ![]() That replace has now rolled out (opens in new tab), so Firefox customers ought to hopefully see noticeably higher efficiency. So so far as I perceive, solely customers that might explicitly reject definition updates (which doesn’t sound like one thing affordable to do together with your AV) wouldn’t get the repair.” “This consists of even Home windows 7 and eight.1 customers, though these platforms shouldn’t have had the efficiency concern with Firefox within the first place as a result of the ETW occasions that trigger it don’t exist on these older variations of Home windows. “In line with Microsoft, this might be deployed to all customers as a part of common definition updates, that are packaged independently from OS updates,” Yannis Juglaret, a Mozilla developer, wrote on Mozilla’s Bugzilla message board final month (opens in new tab). Thankfully, the problem appears like it’s resolved in the end. ![]() The bug, which is tied to Home windows Defender’s Antimalware Service Executable course of, has been recognized to supply high-CPU utilization when working Firefox in comparison with Google Chrome and Microsoft Edge. Higher late than by no means, I suppose, however Microsoft lastly received round to fixing a five-year-old high-CPU utilization bug in Mozilla Firefox. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |