Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Avatar for Username

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Тази тема беше архивирана. Моля, задайте нов въпрос ако имате нужда от помощ.

Firefox 3.6 has a memory leak with Winamp Toolbar on Windows 7

  • 1 отговор
  • 39 имат този проблем
  • 1 изглед
  • Последен отговор от Tauramandil

FrostNGlow
FrostNGlow
more options

I recently installed the Winamp Toolbar and everytime I closed FF, it would hang and stay open and my CPU would be 100%. The only way to shut it down was thru the task manager. It took me some time to figure out exactly what the problem was but after uninstalling just the Winamp Toolbar, FF closed smoothly. So, im pretty positive it has to do with Winamp Toolbar. I have contacted Winamp but with no response.

I am running Windows 7 Premium Home Edition (64-bit) and Firefox 3.6.10.

I recently installed the Winamp Toolbar and everytime I closed FF, it would hang and stay open and my CPU would be 100%. The only way to shut it down was thru the task manager. It took me some time to figure out exactly what the problem was but after uninstalling just the Winamp Toolbar, FF closed smoothly. So, im pretty positive it has to do with Winamp Toolbar. I have contacted Winamp but with no response. I am running Windows 7 Premium Home Edition (64-bit) and Firefox 3.6.10.

Всички отговори (1)

Tauramandil
Tauramandil
more options

I wanted to add that I've been having this problem as well. I believe it is not OS specific, because I've been having this both on my XP & my windows 7 ( both 32bit home editions).

I can add that just disabling the addon suffices to prevent the problem. But if you can't use it, you're better of uninstalling it anyway