تلاش سپورٹ

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

مزید سیکھیں

Since the Version 20.0 update when starting firefox I have frequently got the error message "firefox is having trouble your windows and tabs" .

  • 2 جواب دیں
  • 16 میں یہ مسئلہ ہے
  • 5 دیکھیں
  • آخری جواب بذریعہ DougHoward

more options

Since the version 20.0 update when starting firefox I have frequently got the error message "firefox is having trouble recovering your windows and tabs" This has not occurred with previous versions. If I click on the box "restore" and close firefox the problem reoccurs if I click close I lose the bookmark sidebar. I am so sick and tired of these frequent and buggy updates (every one since 17.0 have caused norton 360 to stop detecting tracking cookies for several weeks and or broken the norton toolbar) that I will uninstall firefox and switch to another browser if this does not change.

Since the version 20.0 update when starting firefox I have frequently got the error message "firefox is having trouble recovering your windows and tabs" This has not occurred with previous versions. If I click on the box "restore" and close firefox the problem reoccurs if I click close I lose the bookmark sidebar. I am so sick and tired of these frequent and buggy updates (every one since 17.0 have caused norton 360 to stop detecting tracking cookies for several weeks and or broken the norton toolbar) that I will uninstall firefox and switch to another browser if this does not change.

تمام جوابات (2)

more options

See:

If you have submitted crash reports then please post the IDs of one or more crash reports that have this format:

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

You can find the IDs of the submitted crash reports on the about:crashes page.

  • You can open the about:crashes page via the location bar, like you open a website.

See:

more options

From checking other users feedback It appears lots of other users have this problem with firefox 20.0 - At least acknowledge that this is a bug in firefox 20.0.