Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Search Support

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.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Firefox crashes

  • 2 antwoorde
  • 1 het hierdie probleem
  • 4 views
  • Laaste antwoord deur knorretje

more options

I've been having problems with Firefox hanging up and "not responding". I went to safe mode and disabled extensions, but when i went to restart, it started crashing and now won't open at all

I've been having problems with Firefox hanging up and "not responding". I went to safe mode and disabled extensions, but when i went to restart, it started crashing and now won't open at all

All Replies (2)

more options

Create a new profile as a test to check if your current profile is causing the problems.

See "Basic Troubleshooting: Make a new profile":

There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins" in case there are still problems.

If that new profile works then you can transfer some files from the old profile to that new profile, but be careful not to copy corrupted files.

See:

See:

If you have submitted Breakpad crash reports then post the IDs of one or more Breakpad crash reports (bp-xxxxxxxx-xxxxxxxxx-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

Your crashreport:
https://crash-stats.mozilla.com/report/index/bp-305ba9b9-3464-4fc8-8fad-99bfb2111109
Firefox 8.0 Crash Report [@ DbgBreakPoint ]
This seems to be caused by Roboform. Installing the latest version 7.6.2 of Roboform should solve this problem according to the Related Bug 691271.