Talk:Problematic extensions

From MozillaZine Knowledge Base



Is workaorund of 3'rd Adblock problem correct? I guess there should be: "If you have Quicktime plugin, keep the OBJ_TABS setting disabled" ..Stef

Adblock and Adblock Plus ActiveX issue

I updated these sections based on the following private message received today. Alice Wyman 16:26, 7 August 2006 (UTC)

I noticed that you added a section in Problematic extensions telling that Adblock Plus has issues with the ActiveX plugin. This is not up to date any more, Adblock Plus and higher uses a work-around to avoid this problem. Furthermore, the actual problem has been fixed (bug 340852) though not checked in on branches yet. Could you adjust the description in the knowledge base? I would do it myself but I am not registered there.

regards Wladimir Palant

"Memory leak" in Adblock Plus

I removed the following problem supposedly caused by Adblock Plus: "Delays release of memory caused by closing a tab". Reference was bug 213391 comment 56 (suggested solution was mind-boggling: replace Adblock Plus by Adblock). This issue was never officially confirmed and seems to be based on a misunderstanding of how memory management in Firefox works: only memory at the end of the reserved block can be released to the OS. In this particular case Adblock Plus caused memory to be allocated after the memory for the most recent tab - which prevented it from being released to the OS immediately and was interpreted as a memory leak. Anyway, the behavior changed with Adblock Plus so that in this particular case memory is released to the OS immediately now (which is probably not representative). --Wladimir Palant 21:13, 12 December 2006 (UTC)

Wizz RSS

I noticed that no reference was given for the Wizz RSS 2.0.0 update issue workaround (Reinstall Firefox) added by Rturnham on 18 November 2005. I did find a recent mozillazine forum thread [1] so I added a link to the thread as a reference and changed the workaround to the one given in the thread (uninstall in Safe Mode). Alice Wyman 04:56, 21 November 2005 (PST)


Could someone add ProCon to the list, it will replace all words with asterisks if set to "censure" words. (example) Unfortunately I'm not entirely sure I understand how to edit pages like this one with tables...--Lethargy 01:35, 15 May 2006 (UTC)

I agree that the Table format is daunting to new editors. I had problems when I first tried adding a new entry to the list until I figured it out by trial and error, patterning my new entry against an existing one and previewing my results. I added ProCon to the list (compare in History to see how I did it). Go ahead and fix up what I added (if necessary) since you have first-hand experience with ProCon and I don't. Alice Wyman 11:48, 16 May 2006 (UTC)
Thanks for doing that, perhaps I'll learn to do it myself dome day :). I don't see any reason to edit what you have added.--Lethargy 19:31, 16 May 2006 (UTC)


I really don't see the need for a contents list at the start. The list is alphabetical and non-hierarchal and short. It's incredibly easy finding what you're looking for, and adding a contents list just adds length and requires maintenance. If anything, we should give each extension its own second-level heading and let Wiki make a table of contents. --Np 17:37, 2 December 2005 (UTC)

Np, I forgot that the list was alphabetical until I saw you moved Fasterfox from the bottom, where I had added it. Sorry about that. Alice Wyman 17:04, 20 December 2005 (UTC)

Fair enough. I did try the second-level-heading approach first but I couldn't get it to work properly. Maybe you'd have better luck? --Vectorspace 10:52, 19 December 2005 (UTC)

Changed intro. You have to get users' attention!

I'm tired of people glancing at this list, not seeing their extensions or their symptoms, and declaring that the problem cannot be an extension. For a long time we have have a warning in italics that the list is not comprehensive and that there can be other problems that are not listed. They still don't read it. So now I have made the advisory even more explicit and put it in BOLD italics. PLEASE DON'T CHANGE THAT. It's not overkill. People have to read that. And yes, I had to add two sentences, but they are necessary.

I also short-circuited the Standard Diagnostic by saying they should try safe mode. I suspect that few users make it all the way to the end of the SD. If the problem is extensions, they should go right to safe mode. --AnotherGuest. 31 Jan 07

Safe Mode does not reset preferences changed by some extensions

It should be noted that for one extension (at least) namely Fasterfox. Safe Mode doesn't fix the changes it makes in about:config --Malliz 14:42, 7 June 2007 (UTC)

Good point . Same with the QuickJava extension, which lets you disable and re-enable Java and JavaScript using a button in the status bar (toggles the javascript.enabled and security.enable_java preferences) instead of using "Tools -> Options -> Content". Running Firefox in Safe Mode doesn't re-enable those settings if disabled by the extension. The Safe Mode article should probably mention it as well. Alice 16:04, 7 June 2007 (UTC)
I removed the suggestion to use Safe Mode from the Intro as the standard diagnostic covers Safe Mode and resetting preferences; if the problem persists in Safe Mode then the standard diagnostic suggests a new profile will fix it. I've also edited the Safe Mode article to add that modified program preferences remain in effect in Safe Mode, in both the Intro and in the Safe_Mode#Firefox section. Alice 11:12, 8 June 2007 (UTC)


The formatting of this page isn't all that great. It's difficult to come up with the correct hash to link to a certain item in the page. The table doesn't fit on 800X600 [2]. There's no TOC. I suggest we do something like this instead:


  • All versions. Having the OBJ_TABS setting enabled has been known to interfere with the ActiveX plugin (if installed). It can cause the plugin to ignore its configuration and run any ActiveX control, instead of the controls it is restricted to. Such a situation could potentially be a big security risk. If you have the ActiveX plugin, keep the Adblock OBJ_TABS setting disabled, or update to Firefox or later versions, which include a fix.[2][3]
  • All versions. Having the OBJ_TABS setting enabled will interfere with the Java plugin. Java applets will not display unless this setting is disabled. If you want Java applets to display, keep the Adblock OBJ_TABS setting disabled.[4][5]


--Np 23:36, 12 March 2007 (UTC)

I agree. The table is also annoying to edit and discourages new editors from attempting it. Alice 23:34, 12 March 2007 (UTC)
If we make it a template, we can easily change the format in the future and avoid repetition. I threw one together with an example of usage at User:Np/Test.--Np 16:53, 26 March 2007 (UTC)
If no one objects, I'm going to change the page to the new format soon.--Np 20:34, 22 May 2007 (UTC)

Removing entries for old issues that have been fixed

I'm not objecting, just observing that this article has quite a number of entries now and will most likely continue to grow as new entries are added, unless more of an effort is made to weed out extension issues that have been resolved in updated versions. Also, some extensions listed have multiple issues (e.g. Adblock, Adblock Plus, NoScript, Google Toolbar, Tabbrowser Preferences) and it might be worthwhile spinning these off to separate articles to make this page easier to navigate and to increase the "signal-to-noise" ratio of useful information to irrelevant clutter, for the benefit of users who don't have those particular extensions installed ;-) Alice 10:51, 23 May 2007 (UTC)
Just kidding on that last suggestion to spin off separate articles. Alice 12:06, 23 May 2007 (UTC)
How about anything that has a new version on AMO and the last problematic version was released over 6 months ago can be removed?--Np 18:45, 23 May 2007 (UTC)
I have no problem with people removing content as long as it is done for a good reason and it's documented in the summary or on the discussion page. I was thinking of removing the old Adblock (Firefox 1.0.x) issue myself (but never got to it). We really do need a KB review process. Hopefully the KB "inventory" process will help flush out outdated Firefox article content. Alice 19:55, 23 May 2007 (UTC)

I think it's time to remove problems with extensions that are not compatible with Firefox 2, because people still running Firefox 1.5 that are having problems will be advised to update to a new version or create a new profile anyway. How can we determine which extensions are not compatible with Firefox 2? I just tried to see if I could remove the information on AdBlock, and all I can find about it is that it was released January 15, 2006. I also see that Adblock Plus was released 2006-06-08. I guess we'll have to find a cutoff date and remove any problems with extensions before that date. Because Firefox 2 was released in November 2006, I propose removing problems with extensions that were fixed in or before September 2006. Does that seem like a good cutoff date? -- schapel 13:21, 9 October 2007 (UTC)

A September 2006 cutoff wouldn't work if you want to eliminate extensions that are not compatible with Firefox 2. Extensions are also written to be compatible with testing builds, like 2.0b1 in the case of Adblock, the current version, which was released on June 30, 2006 and is marked compatible with 2.0.0.* You could remove Adblock issues for versions "Prior to" as a start, anyway, since those issues have been fixed in a version that was released over a year ago. I would go along with removing any extension where the issue has been fixed in a version released over six months ago. Alice 15:21, 9 October 2007 (UTC)
I wouldn't be comfortable removing problems that were fixed just six months ago. Many users are using older versions of Firefox (for example, about 5% of Firefox users are still using Firefox 1.5). It makes sense that many users are using older versions of extensions. Maybe remove issues that were fixed more than a year ago, to strike some balance between keeping old information for users who use old extensions, and removing information that is very old? schapel 20:21, 10 October 2007 (UTC)
Removing issues that were fixed more than a year ago is a good place to start weeding out old entries. Alice 23:45, 10 October 2007 (UTC) OK, I just removed the two Adblock issues for versions "Prior to" for the reasons given above (I was editing the article anyway). Alice 16:59, 11 October 2007 (UTC)
What should we do about problems that may be fixed in a newer version? For many problems I've added recently, I simply put the version of "All?" because I don't know what versions have the problem. Maybe we should change every "All?" to be "<Version> and prior?" where <version> is the current version of the extension. If we get no confirmation that the problem exists in newer versions, we would remove the problem more than one year after the release of the next version. Again, it isn't a perfect solution, but it may strike a balance between removing outdated information from the page and keeping information about problems around for long enough to be helpful. -- schapel 20:21, 10 October 2007 (UTC)
Agree, as far as putting "<Version> and prior?" instead of "All?" when we don't know the specific versions having the problem. As for your suggestion that If we get no confirmation that the problem exists in newer versions, we would remove the problem more than one year after the release of the next version, I'm not sure if items should be removed just because more than one year has passed since the release of a more recent version. At the very least, we should add a section here proposing removal if the old entry and allow some time for feedback. Alice 00:07, 11 October 2007 (UTC)
Just to clarify, I certainly agree that we should remove entries for extension issues that have been documented as fixed over a year ago. Alice 13:52, 15 October 2007 (UTC)

Skype V2.2.0.67

There have been a few reports on the forum concerning this extension and the address bar. It seems it will cause the address bar to be blank and not update when switching tabs or going to the next link. They're may be another problem, I'll ask one of the forum regulars if he knows it, because he pointed it out to me once before. Uninstalling has been correcting the issue.

As I'm new to editing the KB, I'm adding this section to the talk page in the hopes that someone else can edit the page. As I gather some more info, I'll post it here.

Current version is and may correct the problem.
^ 19 April 2007 by Smsmith

Could you post a link to the extension (preferably at as well as a reference link to one or more of the forum tropics where this problem is discussed? Also, make sure you sign your comments here.... there's a little "Signature" icon you can click to add it and a timestamp, or you can use four tilde (~~~~) at the end of your comment, like I do. Thanks! Alice 00:12, 20 April 2007 (UTC)
Thanks for tips Alice. I'm still gathering version information, but here are some more symptoms and forum links.
At the user describes his back and forward buttons not working. Disabling skype extension seemed to have cured it.
And at the user describes the searchbar button and possibly some content buttons (like submit in the forums) as being broken. Again, disabling/uninstalling skype seemed to solve it.
  Here is a discussion on the Extensions Mirror forum re this problem
  Also more reports of the problem

--Malliz 06:00, 20 April 2007 (UTC)

Skype lives here at addons:
But it may be this one:
--Sean 02:47, 20 April 2007 (UTC)
Looks like the second link is the one for the toolbar extension. As far as I can figure, the "Skype Sidebar 0.4.2" (addon/2231 link) and the "Skype Toolbar for Firefox Version:" (skypewebtoolbar/firefox link) are different addons for the "Skype" program, currently at Version 3.1 for Windows. The Extensions Mirror forum link given above includes download links to the program and the toolbars. I found another page for Skype at the Extensions Mirror HERE that might be the best link to use in the article since it gives a nice summary. I haven't looked at the mozillazine forum posts and I'm pressed for time right now but I'll see if I can put together an article entry for this, if no one else wants to give it a shot. Alice 16:11, 20 April 2007 (UTC)

I added an entry for Skype. Please fix it up or let me know if I got anything wrong. Alice 00:44, 24 April 2007 (UTC)

Page Text to Link

Posted to User_talk:Castaban:

Hi, Castaban. I see that you contributed yesterday to the Problematic extensions article by adding an entry for a "Page Text to Link" extension, that it Makes "Page Update Checker" extension stop to work with the solution being to Uninstall the extension. Could you add a link to the extension and a reference, such as a MozillaZine forum thread or other web page reference? I did a search at and at on "Page Text to Link" and came up empty. Thanks, Alice 23:55, 10 April 2007 (UTC)

Since nothing came of it, I'd like to remove the "Page Text to Link" entry from the article, if no one objects. It can always be added back if Castaban or anyone else has more information to add, at the very minimum a link to the extension and a comment here describing the problem. Alice 00:12, 20 April 2007 (UTC)

"Page Text to Link" removed since no one responded. Alice 00:44, 24 April 2007 (UTC)

Netcraft Toolbar

I have noticed a few people having trouble with this extension lately see Has anyone seen problems relating to it? It may need to be added to the list A new version is available on Addons --Mal 13:58, 4 August 2007 (UTC)

The original poster in that thread didn't say his problems connecting to certain sites or to the addons.mozilla site was fixed by uninstalling the Netcraft Toolbar extension; in fact, a new profile didn't fix it. I can't figure out what problem the "guest" had that uninstalling the toolbar fixed. Anyway, someone here recently reported an issue with an empty Bookmarks Toolbar and missing Help menu in Firefox which was fixed by uninstalling the Netcraft Toolbar. The add-ons page says the bookmarks toolbar problem is hopefully fixed in Version If you want to add that issue or if you find other issues reported, feel free to add an entry for Netcraft Toolbar. Alice 17:57, 4 August 2007 (UTC)


Alvin777 reported:

Extension: ImgLikeOpera (ILO)

Versions affected: Checked on 0.6.15

Problem: "Refresh images in tab on tab select" option causes excessive CPU usage on tab change and erratic text box behaviour (i.e. losing caret after selection in google search text box).

Workaround: Turn off "Refresh images in tab on tab select" option. --

Behavior is easily confirmed on my computer. Significant tab change delay (with corresponding 100% CPU usage shown by Process Explorer) is seen when switching to tab with google reader.

See his post on Mozillazine

--Mal 02:42, 15 September 2007 (UTC)

Added ImgLikeOpera entry based on the above Alice 04:02, 15 September 2007 (UTC)

Burn4Free Toolbar

Burn4Free toolbar version (?) was added today by new user, "Deliriouslyhappy" [3]; however, no reference was given. I checked the link to the "extension" and the download is for burn4free_setup.exe. We really need to have more information to justify this entry; otherwise, I think it should be removed. Alice 23:15, 5 October 2007 (UTC)

Burn4Free toolbar Gray bar below the status bar with red arrow. Uninstall Burn4free toolbar

I removed the above entry. Alice 23:54, 10 October 2007 (UTC)

ThinkVantage Password Manager

ThinkVantage Password Manager version 2.0 was added today by new user Jmstuckman [4] <snip> I posted to User talk:Jmstuckman today asking for references. Alice 14:47, 2 November 2007 (UTC)

It's not an extension. I have configured four new Lenovo laptops recently, and there definitely is a ThinkVantage Password Manager that is enabled by default and which I promptly turn off. However, it is not a Firefox extension; it does not appear in the Add-ons lists. It's part of the ThinkVantage Productivity Center, which is a separate program. Before I disabled it on the laptops, I didn't notice any freezing; I disabled it because it was confusing to have two different prompts for remembering passwords. -- schapel 14:23, 9 November 2007 (UTC)

Here is part of what I posted on JMstuckman's talk page:
I see that you contributed to the Problematic extensions article by adding an entry for ThinkVantage Password Manager 2.0. You said, "Firefox freezes for 5 seconds when new windows are opened. Note that this extension is installed by default on Lenovo Thinkpad laptops." <snip>. (By the way, in searching for references myself, I found How-to use ThinkVantage Password Manager with Firefox 2.0 and Users must manually install the ThinkVantage Password Manager 2.0 Extension to enable FireFox browser support. These pages say that the Firefox extension, at one time at least, needed to be manually installed.)

Here is an excerpt from the second reference, from

To install the ThinkVantage Password Manager 2.0 Extension for FireFox, complete the following procedure:
1. Open Firefox.
2. Click File, click Open File, then select the tvtpwm_moz_xpi.xpi file from the location where the Client Security Solution application is installed. For example "C:\Program Files\Lenovo\Client Security Solution". The Software Installation window is displayed.
3. Click Install Now.
4. The plugin is displayed in the Extensions window while installing. A message prompting you to restart Firefox to complete the installation is displayed.
5. To verify that the .xpi file installed correctly, restart Firefox.
6. Click Tools, then click Extensions. ThinkVantage Password Manager 2.0 should be displayed in the extension list.

....even so, since the person who added the entry hasn't responded even to state that he himself experienced the issue, and since you have confirmed that the Firefox extension is not installed (does not appear in the Addons window) by default then I think the entry should be removed from here and from the Firefox hangs article. I posted a follow-up to User talk:Jmstuckman just now linking back to this discussion. Alice 16:46, 9 November 2007 (UTC)

Ah, I see. I just tried the extension. It does actually cause about a one second delay in opening a new window. I have the latest, fastest ThinkPad available, so it may be that some users could see a delay of up to five seconds. Now that I see what the problem is, I think the information should stay. It should be clarified that this applies to the extension that needs to be manually installed, and that it may cause Firefox to freeze for up to a few seconds. -- schapel 17:28, 9 November 2007 (UTC)
OK. I see you've edited the entry and linked it to the ibm page that says it needs to be manually installed. Alice 19:53, 9 November 2007 (UTC)

Menu Editor

Apparently, Menu Editor ( ) is killing off wheel clicking to open a new tab.

Is this worth an entry or should I wait to see if the problem wasn't specific to the posters' set up?

--LoudNoise 22:21, 18 April 2008 (UTC)

The issue has been reported for version 1.2.4 in mozdev bug 18988 Opened: 2008-04-17 22:35 (quote) with the update from to 1.2.4 that just happened today my middle mouse button no longer clicks/opens new links from webpages at all.. rolling back to restores functionality and as a test i then manually updated to 1.2.4 and once again middle clicking on a link is broken. It was also reported (quote) narrowed it down to being incompatible with Gmail Manager extension. When both were enabled, middle click would not work.
According to the Add-ons page for the Menu Editor extension, version 1.2.5 was just released on April 18, which (quote) Fixes middle click bug with Gmail notifier but the bug report isn't yet marked as fixed. I posted to the forum thread asking if the problem still occurs in version 1.2.5 and thrumyeyez replied, The problem still occurs with V 1.2.5. Alice 10:53, 19 April 2008 (UTC)
Added Menu Editor Alice 00:26, 22 April 2008 (UTC)

Moola BoosterBar .38

Per this topic:

Moola BoosterBar .38 apparently causes the tooltip to persist.
^ 17 June 2008 Smsmith

I searched MozillaZine for "Moola" using a custom Google search and the above topic is the only one that came up. I did find some information about Moola BoosterBar at but no direct link to the extension. I found another Firefox user who reported having it installed but didn't mention any problems with it. I'm thinking we shouldn't add it to the list unless someone else reports a problem with it. Alice 22:35, 18 June 2008 (UTC)
Not a problem. I wanted it posted so I wouldn't forget about it. --Sean 03:33, 20 June 2008 (UTC)


The information on Firebug in this page is out of date and inaccurate.

This information on the page about Firebug is false: Causes excessive CPU usage; Firefox may hang when pop-up window is accessed, even if only to close the pop-up.

Firebug does not "cause excessive CPU usage". There are conditions where using Firebug will require large amounts of CPU to be used. This is not excessive and its caused by the user, not by Firebug.

There are no reports, verified or otherwise of pop-up window hanging Firefox with Firebug.

Correct: Firebug adds significant overhead to web page processing of the Console, Script, or Net panels are left enabled; Firebug aids developers and should be disabled when not in use.

This information on the page about Firebug is also false: Causes Firefox to crash on logout from Yahoo! Mail.

There are two reports of Yahoo crashes with Firebug. One was on FF3.0beta 3 with Firebug 1.1 which is no longer distributed. The second was on on FF2.

Correct: Firefox 2.0 will crash in a number of ways while using Firebug, mostly on sites with lots of errors and simultaneous eval() calls. Firefox 3.0 has no crash reports with Firebug by normal users; there are a few crashes involving unreleased advanced features.

^ posted 14 February 2009 Johnjbarton (→Firebug)

I checked the references for the stated Firebug issues. I added this forum reference for the CPU issue reported by a Firefox 3 user. Alice 19:59, 14 February 2009 (UTC) P.S. Regarding There are no reports, verified or otherwise of pop-up window hanging Firefox with Firebug, a report of that is already included in the references for Firebug. [5] Alice 12:16, 15 February 2009 (UTC)
On the Yahoo Mail signout crash I edited the Firebug entry to show that the reports were for Firefox 2 (I found two more references for Firefox 2 but none for Fx3) and noted that v1.3.2 and above of the extension requires Firefox 3 . ( I couldn't find the FF3.0beta 3 reference with v 1.1 you mentioned, by the way, and you didn't link to it) . Alice 19:59, 14 February 2009 (UTC)


Applications that mess up Firefox

Would like to see a link to a similar list of applications. For instance saw a newsgroup posting about Zone Alarm grabbing the Firefox task so that Firefox can't even be cancelled with the Windows Task Manager. FF stops loading on new page [6] (thread not archived yet). DMcRitchie 18:16, 20 February 2009 (UTC)

For instance saw a newsgroup posting about Zone Alarm grabbing the Firefox task so that Firefox can't even be cancelled with the Windows Task Manager. That's mentioned in Firefox hangs#Hang at exit under the bullet point for "If you use ZoneAlarm on Windows Vista", with links to a number of references and bug 470849. Firewalls/security software seem to be the biggest offenders. Norton is also mentioned in Firefox hangs and McAfee is mentioned in Popups not blocked#Other software disables the popup blocker. The Error loading websites article also mentions Firewalls and other security software with some specifics under Error loading websites#Websites randomly do not load. There are also plugin-related standalone applications such as Windows Media Player and Java but those have their own articles that include troubleshooting information,. Just my opinion but "Problematic applications" is probably too wide of a topic to cover in one article. Personally, I think it's better to leave problematic applications the way they're being handled now, in the related article that covers the symptoms. Having a "Problematic extensions" article is a big undertaking and this article is hard to keep current and to remove outdated information, since many extension entries are missing version numbers. I'm afraid that a "Problematic applications - Firefox" or even a "Problematic security software - Firefox" article would be just as hard to keep updated with current information. Alice 21:06, 20 February 2009 (UTC)

System add-ons

None of the KB articles appears to discuss disabling specific system add-ons. This article might be a good place to do that. See Tanstaafl 12:00, 11 August 2017 (UTC)