Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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

This thread was archived. Please ask a new question if you need help.

NEW Firefox 12 on SnowLeopard (10.6.8) hangs on open

  • 1 reply
  • 8 have this problem
  • 1 view
  • Last reply by krabat

krabat
krabat
more options

Have updated along the way, now FF12. It hangs on opening, and consumes 106.4% CPU...

Have dumped plists, but am reluctant to dump profile in Application Support/Firefox/profiles called r97p6mjf.default, as I have a lot of ebooks in the epub plugin.

Upon reinstallation it checked plugins, but then nothing happens. Continues to use over 100%CPU.

Good advice appreciated - especially as I use Firefox as my desktop EPUB reader!

Have updated along the way, now FF12. It hangs on opening, and consumes 106.4% CPU... Have dumped plists, but am reluctant to dump profile in Application Support/Firefox/profiles called r97p6mjf.default, as I have a lot of ebooks in the epub plugin. Upon reinstallation it checked plugins, but then nothing happens. Continues to use over 100%CPU. Good advice appreciated - especially as I use Firefox as my desktop EPUB reader!

All Replies (1)

krabat
krabat Question owner
more options

Removed/saved the profile. Restarted FF. Opens in a flash!

Returned profile parts one by one, with restarts between every one. No hanging.

Even so, I lost access to all of my EPUBs. Plugin no longer recognises them.

So, don't do this.

(Damn!)

Still don't know what the problem was.