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.

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

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.

All Replies (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