![]() ![]() To exit Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again. Please follow the steps in the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article to find the cause. If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, theme, or hardware acceleration. When the Firefox Safe Mode window appears, select "Start in Safe Mode". (you may need to specify the Firefox installation path e.g. On Linux: Quit Firefox, go to your Terminal and run firefox -safe-mode.On Mac: Hold the option key while starting Firefox.On Windows: Hold the Shift key when you open the Firefox desktop or Start menu shortcut.If Firefox is not running, you can start Firefox in Safe Mode as follows: Click the menu button, click Help and select Restart with Add-ons Disabled.If Firefox is open, you can restart in Firefox Safe Mode from the Help menu: Firefox Safe Mode is a troubleshooting mode that temporarily turns off hardware acceleration, resets some settings, and disables add-ons (extensions and themes). If not, try Firefox Safe Mode to see if the problem goes away. His email address is more by Gregg Keizer on, see if anything here helps - Adobe Flash plugin has crashed - Prevent it from happening again. ![]() Follow Gregg on Twitter at on Google+ or subscribe to Gregg's RSS feed. Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news for Computerworld. The newest Flash Player plug-in update applies only to Windows, and patches a bug that caused crashes in Mozilla's Firefox. Firefox users can also wait for Flash's silent updater to automatically download and install the new plug-in. "We continue to work closely with Mozilla to further improve pre-release testing to more reliably catch issues like these," said Adobe in a Thursday blog.įlash Player 11.3.300.262 can be downloaded from Adobe's website. The open-source developer has used its blacklist sparingly, most recently in April, when it disabled older versions of Java during the Flashback malware campaign. Firefox installations automatically query the list and notify users before disabling the targeted add-ons. Mozilla has the ability to disable troublesome extensions or plug-ins by adding them to the Firefox add-on blocklist. Around the same time, Mozilla also "blacklisted" the RealPlayer plug-in, which was contributing to the crashes. "This is on Mozilla's end, even though they completely blamed Adobe for it," wrote someone identified as "Squall_Leonhart69r" on the Adobe bug database.įor its part, Mozilla had spun up a quick update to Firefox, version 13.0.1, and began pushing it to users on June 15. In its own bug-tracking database, Adobe said it could not reproduce the crash, with contributors there chastising Mozilla for blaming Adobe. There was some finger-pointing on Adobe's part as well. ![]() Initial suspicions at Mozilla pointed to Flash Player 11.3's new sandboxed plug-in for Firefox, but yesterday Adobe claimed that there were "different causes" for the crashes, which seemed to be concentrated on Windows Vista and Windows 7 machines. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |