Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Unfortunate thing happened

  • 2 wotmołwje
  • 1 ma tutón problem
  • 6 napohladow
  • Poslednja wotmołwa wot Ranteamo

more options

Every time I delete cookies and stuff, the next time when I open the browser the crash window comes up, where I'm able to restore the previous sessions: about:blank (thats my homepage, so its a total blank white page) But why would I want to restore a white page which is my home page from the begining? This happens at my home computer and here in my work place too. Both have the about:blank homepage. It's not a program breaking bug, but an annoying one. So can I do something about it or should I wait for a FF update? Thank You!

Every time I delete cookies and stuff, the next time when I open the browser the crash window comes up, where I'm able to restore the previous sessions: about:blank (thats my homepage, so its a total blank white page) But why would I want to restore a white page which is my home page from the begining? This happens at my home computer and here in my work place too. Both have the about:blank homepage. It's not a program breaking bug, but an annoying one. So can I do something about it or should I wait for a FF update? Thank You!

Wšě wotmołwy (2)

more options

Hello,

Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Once you get the pop-up, just select "'Start in Safe Mode"

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.

________________________________________________________________________________

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash ID's to help us learn more about your crash.

  1. Enter about:crashes in the address bar (that's where you enter your website URL) and press Enter. You should now see a list of submitted crash reports.
  2. Copy the 5 most recent crash ID's that you see in the crash report window and paste them into your response here.

Thank you for your cooperation!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

Hi,

I'm using the default theme. Safe mode didn't help. But its interesting: I open about 10-10 times in normal and safe mode and about every 3rd try the problem came up. So I don't think its related to deleting browsing history, cookies, etc. The plugins I use at both places is very standard. Java, Adobe, Flash, etc common/standard plugins so I don't think thats the problem. I always used them and always set my homepage to about:blank, but for a few weeks now I have this problem. And becouse its happening in two different cities, two different computer with different program I think its on FF side. Maybe a new update did something with this, not sure.