This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

I can't get Firefox to work (unable to connect) yet IE works fine. Here's the crash ID: ID: 73f9c4c7-86e9-4bfa-b05a-302772140109

  • 3 respostas
  • 4 have this problem
  • 2 views
  • Last reply by cor-el

qwertyrain
qwertyrain
more options

I've tried resetting it to the defaults but that didn't help.

bp-73f9c4c7-86e9-4bfa-b05a-302772140109

(added the crash ID to the thread body - c)

I've tried resetting it to the defaults but that didn't help. bp-73f9c4c7-86e9-4bfa-b05a-302772140109 ''(added the crash ID to the thread body - c)''

cor-el modificouno o

All Replies (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The crash report shows a rather high memory usage: System Memory Use Percentage: 83

The linked bug report also indicate an OOM (out-of-memory) issue:

  • bug 767343 - crash in nsSupportsStringImpl::SetData with abort message: "###!!! ABORT: OOM: file e:\builds\moz2_slave\m-cen-w32-ntly\build\xpcom\string\src\nsTSubstring.cpp, line 348"

Note that the bug shows a fixed status that has been back ported to the current Firefox 27 beta release, so you could give the Firefox 27.0 beta version a try. This beta version will become the next release in February (Feb 4).

qwertyrain
qwertyrain Question owner
more options

Thank you for your response. Is switching to the new beta release only choice? Is there no way of fixing and keeping this version? Someone told me that Vimeo could've caused it

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You can install the beta version alongside of the current release with its own profile.Then you can check out if this helps to avoid the crashes and can still go back the the release version at any time by clicking its desktop shortcut.

You can install multiple Firefox versions via a custom install in different installation folders and keep the current release version installed to be able to fallback to the release version in cases when the beta build isn't working properly.

Make sure not to start Firefox after the installation has finished and use the Profile Manager to create a new (separate) profile for each version.

Use the Profile Manager to create a new profile for this version, so make sure not to start Firefox after the installation has finished.

Create a desktop shortcut with -P "profile" appended to the target to launch each Firefox version with its own profile.
The "profile" parameter is the name as seen in the Profile Manager and not the folder name on the hard drive.