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

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

Докладніше

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

Version 5.0 will not unload itself from memory when I close it. This results in not being able to open FF later unless I manually go and close the application in Windows task manager. Any ideas as this is getting very frustrating.

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

more options

I have this issue on 3 computers that were just updated with FF 5.0. When I close FF, the application "Firefox.exe *32" remains in memory. Trying to open FF again later greets me with the error that FF can't open because another instance of FF is already running. Previous versions did unload completely and never caused this issue..

I have this issue on 3 computers that were just updated with FF 5.0. When I close FF, the application "Firefox.exe *32" remains in memory. Trying to open FF again later greets me with the error that FF can't open because another instance of FF is already running. Previous versions did unload completely and never caused this issue..

Обране рішення

You may want to check your add-on's for compatability, there may be conflicts.

For the time being, you can use the 'End Task' command in the Task Manager to close Firefox before opening another version.

Читати цю відповідь у контексті 👍 0

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

more options

Вибране рішення

You may want to check your add-on's for compatability, there may be conflicts.

For the time being, you can use the 'End Task' command in the Task Manager to close Firefox before opening another version.

more options

I found the culprit. Norton Internet Security added an add-on to FF called Symantic IPS 2.0 which is causing FF 5 not to close properly. I have no idea what it is for but FF works properly again with it disabled.

For reference, that add-on worked fine with FF 3.x as well as FF 4.x. It just doesn't seem to like FF 5.0.

Змінено Dave_C_64