Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

Every tab crashes, can't use Firefox at all, help?

matt.helfrich1976
matt.helfrich1976
more options

Every tab i try to open crashes. The menu doesn't drop down to refresh or restart in safe mode. I uninstalled and reinstalled, restarted computer, and tried restoring tabs. Crash reports aren't listing anything recent.

Every tab i try to open crashes. The menu doesn't drop down to refresh or restart in safe mode. I uninstalled and reinstalled, restarted computer, and tried restoring tabs. Crash reports aren't listing anything recent.

Alla svar (2)

FredMcD
FredMcD
more options

Start Firefox in Safe Mode {web link}

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

Start your Computer in safe mode with network support. Then start Firefox. Try Secure websites. Is the problem still there?

http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting Any Computer In Safe Mode; Free Online Encyclopedia

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

Hi matt.helfrich1976, sorry to hear about this problem. We are getting multiple reports of "Gah" tab crashes this morning.

In another thread, a user reported this problem could be caused by Bitdefender:

https://support.mozilla.org/questions/1280327

If you have Bitdefender, that could be the culprit. I haven't looked at Bitdefender's support pages to see whether this is a known issue with a workaround.