(Pictured) Firefox 76.0.1 Emergency Release: Fix Problems That Caused Some Extensions to Crash

Just days after The Firefox 76 Stable came online, Mozilla released a maintenance update. The update was released so quickly that it fixed two issues in the Firefox 76 release.

The first of these is a crash on Windows. More specifically, Mozilla found that installing a driver for NVIDIA caused the browser to crash on the 32-bit Windows operating system. The company says only a few devices are affected.

(Pictured) Firefox 76.0.1 Emergency Release: Fix Problems That Caused Some Extensions to Crash

“Firefox 76 had a content crash on 32-bit Windows 7 devices,” the error report reads. It currently accounts for 7% of all tab crashes in the early stages of version 76.0. It seems that Nvidia assigned different names to 32bit and 64bit. We have implemented a 64-bit working method for nvd3d9wrapx.dll. This time the name is nvd3d9wrap.dll (there is no suffix X in the name!). ), apparently 32 thin. Let me prepare a simple patch to solve this naming rule. “

The second bug fixed was to fix the problem of multiple onConnect events in some add-ons, causing them to crash. Extensions, including Amazon Assistant, are affected and may be more widespread, and Mozilla said it received a large number of user complaints after the release of Firefox 76.

Mozilla explains: “The load icon lasts for a few seconds and then displays a message that says, ‘Sorry, I’m having a problem with the loading process.’ This problem can be reproduced 100% on all machines. Since today’s release, we have received multiple customer complaints so far, and given the reproducibility, this issue seems likely to become a common problem as more customers get the latest updates. “

(Pictured) Firefox 76.0.1 Emergency Release: Fix Problems That Caused Some Extensions to Crash

“Our extension uses IFrames and IFrame post-messages extensively in the feature components,” says Mozilla. There is nothing particularly relevant from the release note summary for version 76, but this issue may be related to some changes affecting IFrame communications. Another possibility is anything that specifically affects the browser action API, which is responsible for generating this feature. “

This time, however, it wasn’t just Windows that was affected, as similar problems were confirmed on Linux. This issue has been fixed in this new Firefox update, so if you’ve previously experienced an extension problem after installing Firefox 76, make sure you deploy this build as soon as possible.