0
The latest updates of Firefox security updates may reason for serious system crashes. This left some Firefox users unable to use their browser after upgrading to the latest available version, and now Mozilla suspend the update delivery process until the problem is identified and fixed. Users began reporting the crashes soon after Firefox 3.6.9 and Firefox 3.5.12 were released last week.
According to Mozilla employee Mark Banner in a new Bugzilla entry, "We're seeing lots of these crashes following the recent branch releases. The crashes occur when attempting to start the browser. The layout module apparently fails to initialize, making it impossible to use the application. Just to note, most of the comments [in crash reports] indicated people were running the browser previously, got the update prompt, updated, and then were unable to start after that point," Christian Legnitto, another Mozilla employee, who works on Firefox releases".
This make Firefox to crash anytime on any action and make your systems immediately restarting. The frequency of the crashes is not very high, but their serious impact on usability is very concerning. Because of this Mr. Legnitto requested that updates be turned off temporarily, pending the outcome of the investigation. This issue with all update delivery for the 3.1.*, 3.5.* and 3.6.* Firefox branches was initially stopped by modifying the permissions on the update directories. These changes were reverted back yesterday and a different blocking method was employed for the 3.5.11 and 3.6.8 versions only, where most crashes were observed. Most of Firefox users won't receive the 3.6.9 and 3.5.12 updates released last week, which address numerous security vulnerabilities of critical impact.
The root for the cause has not found yet and Mozilla is still trying get rid of that. The regression of a previously known bug is one of the possibilities that are currently being investigated. Though you can upgrade by downloading the latest versions and installing them manually, but this we do not suggest to do this until Mozilla fix the bug.
The latest updates of Firefox security updates may reason for serious system crashes. This left some Firefox users unable to use their browser after upgrading to the latest available version, and now Mozilla suspend the update delivery process until the problem is identified and fixed. Users began reporting the crashes soon after Firefox 3.6.9 and Firefox 3.5.12 were released last week.According to Mozilla employee Mark Banner in a new Bugzilla entry, "We're seeing lots of these crashes following the recent branch releases. The crashes occur when attempting to start the browser. The layout module apparently fails to initialize, making it impossible to use the application. Just to note, most of the comments [in crash reports] indicated people were running the browser previously, got the update prompt, updated, and then were unable to start after that point," Christian Legnitto, another Mozilla employee, who works on Firefox releases".
This make Firefox to crash anytime on any action and make your systems immediately restarting. The frequency of the crashes is not very high, but their serious impact on usability is very concerning. Because of this Mr. Legnitto requested that updates be turned off temporarily, pending the outcome of the investigation. This issue with all update delivery for the 3.1.*, 3.5.* and 3.6.* Firefox branches was initially stopped by modifying the permissions on the update directories. These changes were reverted back yesterday and a different blocking method was employed for the 3.5.11 and 3.6.8 versions only, where most crashes were observed. Most of Firefox users won't receive the 3.6.9 and 3.5.12 updates released last week, which address numerous security vulnerabilities of critical impact.
The root for the cause has not found yet and Mozilla is still trying get rid of that. The regression of a previously known bug is one of the possibilities that are currently being investigated. Though you can upgrade by downloading the latest versions and installing them manually, but this we do not suggest to do this until Mozilla fix the bug.
Subscribe to:
Post Comments (Atom)
0 Responses to “ ”
Post a Comment