Firefox crashes when accessing general tab in options
Firefox recently auto-updated to version 33.1. As part of the update, whenever I open a new tab, the system defaults to tab where mozilla shows 10 sites with a mixture of sites I frequently visit and sponsored sites. I had already configured my home page and for new tabs to be "Speed Dial", but this option was overridden with the update.
I wanted to change it back, but now when I try to access the general tab in options (or privacy for that matter), firefox crashes. More accurately, it hangs indefinitely and then I am forced to restart the program.
How can I correct this error so that I can access my options again?
OS information added through Troubleshooter
Speed dial, available here: https://addons.mozilla.org/en-US/firefox/addon/speed-dial/ I can see the most recent comment is that another user cannot use speed dial at all with the new build
Todas las respuestas (2)
There is a Speed Dial support thread over here: http://forums.mozillazine.org/viewtopic.php?f=48&t=540112&start=1020 but it hasn't had much activity this year.
As far as User Reviews, Morcas reported a problem with the alpha1 level Nightly version, which is now Firefox 36 - three full versions newer than what you are talking about and won't become a release until late Feb 2015.
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
- Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
- Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste that into the "Post a Reply" box. (Please don't take a screenshot of your crashes, just copy and paste the ID's. The below image is just an example of what your Firefox screen should look like)
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
Here are the last 5 crash reports that start with bp, but none of the time stamps for date submitted match the occurance of the crashes I am referencing above.
bp-a4832ef4-f8ea-4df3-b3aa-a5d012141108 08/11/2014 9:32 AM bp-94d56c40-f4c1-4f2e-b8ea-2375c2140921 20/09/2014 8:10 PM bp-2570f9dc-7bf7-4ccb-b11e-0ed3a2140830 29/08/2014 7:20 PM bp-36e28585-7c73-44b4-a17a-e123b2140830 29/08/2014 7:14 PM bp-214ac089-6eed-4158-8eed-c62c62140830