This is a tracker for various Gecko issues triggered by Adblock Plus as well as bugs blocking Adblock Plus development.
** STOP Button becomes 'no-op' when ad filtering. **
With FF3.0.6 (on Windows Vista), at various times the STOP button is active but it does nothing - clicking it engages a "no-op" (no operation).
Famously happens on hotmail. You can click on a folder and the 'M' animation
will churn for hours, and one of two outcomes happens: 1)you click on the
active "Stop" button and nothing happens - The Birds still sing and everything
still churns, churns, churns; or 2)the animation churns and the stop button is
inactive and you can't get the damn thing to stop (except by clicking some
other active link on the current page, forcing FF to load that page, and then
stopping THAT second/different operation). On Case #1, the status message is "Transferring from ... " and the status bar is moving or active. If I turn off ABP, this does not appear to ever happen (can't prove a negative 100%). Seems ABP needs to itself be aware of the STOP button or the communication from FF to ABP about the STOP button is corrupt.
Basically, then: 1)often the STOP button does not stop everything, or 2)during
various loading operations the STOP button is not active.
STOP should be like "kill -9" from the old Unix days - it should absolutely
stop whatever is going on, no exceptions. The ABP 1.0.1/FF3.0.6 *STOP* does not do this.
Thought this was related to Bug #151499, but did more research and placed a description here.
Robin, this is not the right place for bug reports. Please use Adblock Plus forum (http://adblockplus.org/forum/index.php) or Adblock Plus bug database (http://adblockplus.org/en/bugs). If you think you found a Firefox bug - feel free to file a new bug at bugzilla.mozilla.org and mark it as blocking this bug.
ive got me a problem with ABP too after a firefox update to 3.6.11, i think its up to mozilla to fix it
ABP simply wont work and jams the addons
THIRD TIME NOW AND GETTING SICK OF IT
tinus, please see my comment 2 just above yours.
It's nice to see additional work being done on this for the last 3 years. :)
I just caught Nightly (29.0a1) using up over 4GiB(!) of RAM which was caused by AdBlock Plus (I use AdBlock Edge but it's the same codebase). It's now hanging around 430MiB since I have various other extensions installed.
The massive memory leak resided in the heap. Firefox doesn't seem to want to free it up for some reason. I've disabled the extension for now.
Shane, this is not the right place for bug reports. Please use Adblock Plus forum for this (http://adblockplus.org/forum/index.php). This bug is meant to track Firefox issues affecting Adblock Plus.