Овај сајт ће имати ограничену функционалност док га будемо ажурирали у циљу побољшања вашег искуства. Ако неки чланак не реши ваш проблем и желите да поставите питање, на располагању ће вам бити наше заједнице подршке @FirefoxSupport на Twitter-у и /r/firefox на Reddit-у.

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

private browsing crash

  • 19 одговорa
  • 6 има овај проблем
  • 1 преглед
  • Последњи одговор послао gnarly0531

more options

Ok now i realize that the update has private browsing open in a new window, however there is a problem with it. It leaves the original window open so i close it because i only want the private browsing open when i private browse (this is why this idea of private browsing opening a new window is stupid, who ever thought it was a good idea should be fired; i mean why would i want a private session AND and non-private session open at the same time?) but anyways by closing the non-private session this cause firefox to close improperly and CRASH. every time i close my private window and come back later to open a new session (non-private default session) i get the "oops this is embarrassing" crash page. literally every time i use private browsing and come back later for a new session i get the crash. what a joke. again why did you change it there is no need for a separate window to open, there is no convince to it as hitting Ctrl-Shift-P to go back and forth between private and non-private is not an issues for any of your users, but now this new stupid system is guess what? an issue for your users, good job guys.

Ok now i realize that the update has private browsing open in a new window, however there is a problem with it. It leaves the original window open so i close it because i only want the private browsing open when i private browse (this is why this idea of private browsing opening a new window is stupid, who ever thought it was a good idea should be fired; i mean why would i want a private session AND and non-private session open at the same time?) but anyways by closing the non-private session this cause firefox to close improperly and CRASH. every time i close my private window and come back later to open a new session (non-private default session) i get the "oops this is embarrassing" crash page. literally every time i use private browsing and come back later for a new session i get the crash. what a joke. again why did you change it there is no need for a separate window to open, there is no convince to it as hitting Ctrl-Shift-P to go back and forth between private and non-private is not an issues for any of your users, but now this new stupid system is guess what? an issue for your users, good job guys.

Сви одговори (19)

more options

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

I doesn't have any of them listed in there, all of the listed crashes are from march.

more options

I can't replicate this problem. It might be something specific about your configuration that didn't arise in testing.

  • Did the window you initially closed use Flash?
  • When you're done with your private browsing, if you open a non-private window and close private then non-private, does that make any difference?

If you want to start directly into private mode, you could create a second Firefox shortcut for those occasions and add this to the command line:

-private

More info on command line switches: Command Line Options - Mozilla Developer Network.

more options

It is looking like firefox is trying to recover tabs from the private browsing which of course it cant because it didn't store info on the session. this is my best guess to what the problem is i guess it isn't a crash more of bug. it opens and says it can't recover my tabs from my previous session one or more tabs may be causing the problem and it has a list of tabs the only one being listed says about:blank. which is my "homepage" setting but its also something firefox should be able to "recover" as it is only a blank page.

here is a print screen of it.

Измењено од стране gnarly0531

more options

so it seems that the problem has been given up on. thanks for nothing guys. still dont see any logic in opening another window for private browsing other than eating up more ram than required. but cool keep making changes that no one wants and that cause problems and more people will switch to chrome.

Измењено од стране user633449

more options

I don't think it's fair to say that "the problem has been given up on." I tried your scenario and didn't get a crash. Unless there are steps to re-create the problem on other installations of Firefox, when you enter it into the bug system, there's no way to track down and fix it.

Could you try a new profile and see whether you can replicate the problem there? To do that, use the profile manager:

  • Exit Firefox
  • Start > search box > firefox.exe -P {ENTER}
  • Create a new profile with the default location setting
  • Start Firefox in the new profile and run your test

Any difference? Any crash ID in about:crashes?

To switch back to your normal profile, restart the profile manager and start up in your regular profile.

Измењено од стране jscher2000 - Support Volunteer

more options

Try Firefox beta. There was a bug fix that might help with this. http://www.mozilla.org/en-US/firefox/beta/

more options

You can check for problems with the sessionstore.js and sessionstore.bak files in the Firefox profile folder that store session data.

Delete the sessionstore.js file and possible sessionstore-##.js files with a number and sessionstore.bak in the Firefox profile folder.

Deleting sessionstore.js will cause App Tabs and Tab Groups and open and closed (undo) tabs to get lost, so you will have to create them again (make a note or bookmark them).


Make sure that Session Restore is working properly.

more options

can you just link the last version before the most recent update cause it also logs me out of all my "keep me logged in" sites so its getting very annoying.

more options

Did you get a chance to do the new profile test? It only take a couple of minutes.

Per your request: Install an older version of Firefox.

more options

yeah i typed what you said but it didnt do anything just opened my usual browser window

more options

If firefox.exe -P just opens a regular window, Firefox did not exit successfully. You have to completely exit all Firefox windows first.

If Firefox is not shutting down properly when you exit, there could be a hung process. The support article has a section on that: Firefox hangs when you quit it.

more options

well i got a new profile to work and seems to fix the issue but man was it fun getting all the add ons and saved passwords restored, seriously do some ******* testing before these "updates" that cause us more issues than they fix cause it is a joke. and again drop this whole private "window" bs its a waste or at least give us an option OMG GENIUS you should hire me on since i have such innovative ideas, oh wait no pretty basic idea there to give your users a choice and not force crap on them.


Edited by a moderator due to language. See the Rules & Guidelines .

Измењено од стране the-edmeister

more options

Hi gnarly0531, the purpose of the new profile was just for testing. Had you reported back that had worked, the next step would be to use the Reset feature which does at least migrate your bookmarks and saved passwords. Sorry I didn't mention that, would have saved you some time.

more options

well i figured that since it was something in that profile that was causing the issue it wouldn't be a good idea to transfer settings and what not as it may transfer the problem with it.

more options

now i dont get the crash but fire fox continues to log me out of "keep me logged in" sites at random intervals not necessarily when i use private browsing, whats up with this?

more options

When you let a site set cookies in a private window, those cookies only work in private windows and are not retained between sessions.

For cookies set in regular windows, they should be retained according to the rules in the Options (e.g., keep per site request vs. allow for session only) and your settings for clearing private data at shutdown, if any. Cookie-related add-ons, external security software, and system cleaners may clear cookies separate and apart from the built-in settings.

Can you see any pattern in the interval of clearance?

more options

If the problem relates to Yahoo or sites in the AOL family, these are sensitive to your proxy setting for some reason. You may have better results choosing No Proxy in your connection settings here:

orange Firefox button (or Tools menu) > Options > Advanced > Network mini-tab > "Settings" button

more options

yeah it is in non private browsing cookies are set to stay saved at shutdown. my anti virus does not clear cookies. no pattern in the interval, an not aol or yahoo site, it happens on things like netflix and various forums