Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Firefox 8 was working fine on my MAC (OSX.5.8) and then began crashing on start-up.

  • 3 відповіді
  • 6 мають цю проблему
  • 1 перегляд
  • Остання відповідь від cor-el

more options

Following Mozilla suggestions I tried deleting and reloading Firefox. It downloads ok, but as it is being copied to my applications folder I notice the copying stops about 1/3 of the way through and consequently continues to be unable to open without crashing. Suggestions? edit

Following Mozilla suggestions I tried deleting and reloading Firefox. It downloads ok, but as it is being copied to my applications folder I notice the copying stops about 1/3 of the way through and consequently continues to be unable to open without crashing. Suggestions? edit

Усі відповіді (3)

more options

Can be caused by a Java update.

See:

more options

Hi,

I just posted more information about the problem following instructions from Mozilla. As you read it perhaps you'll have an idea about what else I can do. Thanks for your help.

more options

Please do not create a new (duplicate) thread about the same problem, but keep the posts in this thread to avoid confusion.


From [/questions/897761]

OOPS! Sent wrong crash report ID below is the correct one. FF 8 was working for a few days after I upgraded to it and then it crashed and continues to crash as I try to start it. I tried deleting it and downloading it again, but that hasn't helped. It also crashes when I try to open it in safe mode. It seems like there is some corruption somewhere in whatever is kept after deleting FF that reappears when I download a new copy. I do not know where legacy data is kept! Below is the most recent ID number, though there are many more before it. This problem is on my wife's computer - an original dual core MacBook Pro (late 2006?) running OSX.5.8.
  • bp-76b8562e-8586-426e-8313-5ec5b2111117