Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

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

  • 1 wotmołwa
  • 39 ma tutón problem
  • 3 napohlady
  • Poslednja wotmołwa wot 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.

Wšě wotmołwy (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