[SOLUTION] AdBlock Plus crashes Firefox

[wintpe]

a pc i look after for my brother in law was having this issue, and it had not been updated for several months.

i saw it happen, it was a mga1 586 system

i had installed adblock 2.12 in all the users browsers.

i updated it and it was still doing it, so versions of firefox 10.0.05 and 10.0.10

disabled adblock and iot fixed the problem.

im running the 2.0.3 from distribution, hence why i was not seeing it.

regards peter

[Glenn]

I've got to toss my hat into the ring here. Firefox is crashing for me too. The current version of Firefox on my Mageia system is 10.0.10 ESR with Adblock Plus installed. I'm using Fedora now since I tried to reply to this thread using Mageia but before I could "post" my message Firefox crashed and all was lost. I am a Fedora user at heart. I also play around with CentOS and Arch and I don't see this Firefox behavior with any of those distributions. I'm sure it is an AdBlock issue and not a Firefox issue, but just the same. Shouldn't happen.

For the record, when I'm running Mageia uname -ra reports Linux mageia2 3.3.8-desktop-2.mga2 #1 SMP Mon Jul 30 21:35:06 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[hintzy64]

What versions of Firefox and Adblock Plus do you have on your Fedora system?

[Glenn]

I'm at work at the moment so I can't check. I could shell in but the box is currently running Fedora. Firefox under Mageia reports itself as 10.0.10 ESR. I'll see if I can report the AdBlock version this evening. Otherwise I'd have to shell into my server, hop over to the Fedora desktop, mount the Mageia partition and hunt around for some AdBlock info.

[digigold]

TBH I've always felt that Mozilla's ESR 10x channel to be unsatisfactory for a variety of reasons. They actually have 5 different release channels:

1- Nightly Builds
2- Aurora (Rolling Alpha release, not unlike Cauldron) Currently at 18.0 alpha 2
3- Beta's (I Actually find this channel to work the best) Currently at 17
4 - Stable (Most used) Currently at 16
5- ESR Currently @ 10 & 17

Now I run Cauldron and other various alpha/beta software so I like the bug-fixes in Beta. In fact I used Aurora for a while and preferred it to stable but not beta. Also Mozilla has release Firefox ESR 17 as a Release Candidate. If I were you I would try either Stable, Beta, or the ESR RC. I know MGA3 gives you the option of either going w/Stable, Beta or Aurora. If MGA2 does not, you can install them manually. (Links: 64bit dl or 32bit d/l)
I have done this with Mageia w/o issue by executing the following:

Code: Select all

# cd /usr/lib64/mozilla
# tar axvf /home/%USER%/Downloads/%FF_FILE%
# cd /usr
# ln -sv ../lib64/mozilla/firefox/%FFBIN% ./


The only issue I believe I had was that I had to update manually. (Firefox's internal update feature did not work.) You could just use your manual install until ESR 17 gets bumped up.

Good luck!

[n00biest]

Adblock Lite 1.4.3 here. & FF 10.0.10. No pb while reaching settings. Nice work all.

[KnightMB]

This must only affect the 10.x version, I kinda skipped that on my Mageia install and went straight to Firefox 17 instead and AdBlock plus is always the first extension I install. So far works without any hiccups. Also on a i586 netbook this is installed and working. For those that must use AdBlock Plus, you can download the latest version from mozilla.com and run it right form whatever folder you extract to. It will pick up the plugins, etc, at least then you will be able to see if the version makes a difference by switching between v10 and v17.

[Skiper]

For those who still experience force closes due to AdBlock Plus in Firefox 10.0.X, there is a functionning workaround to finally bringing back stability. Please read it at https://bugs.mageia.org/show_bug.cgi?id=7237#c8 .

I think this workaround should be provided as an official update for Mageia, since this change prevents crashes from a major extension (and probably others as well) and I believe removes no functionality...unless the mozjs package is updated to prevent these inconveniences.

My two cents...

[filip]

Thanks Skiper. I experienced segfaults since last few days too. The culprit was recent upgrade of AdBlock Plus. I found out that by firefox --safe-mode. After installation of libproxy-webkit (this PC is 32-bit) that was gone. Just in case I removed libproxy-mozjs as suggested in workaround you pointed.

[doktor5000]

I think this workaround should be provided as an official update for Mageia, since this change prevents crashes from a major extension (and probably others as well) and I believe removes no functionality...unless the mozjs package is updated to prevent these inconveniences.

A new bug report should be opened for that, as the two existing ones are already resolved.

EDIT: Ahhh, excuse, has already been done: https://bugs.mageia.org/show_bug.cgi?id=6706

[schnuck68]

Since yesterday FF ESR 10.0.8 with Addons AddBlock Plus, Tab Mix Plus and All-In-One-Sidebar started crashing, too.
But it crashes while starting the browser. So I cannot access the profile anymore.

Tested the following: Started new profile without any Add-On --> everything fine. Added "AdBlockPlus" --> immediate crash. Cannot access the profile anymore. New start crahes while loading the initial page.

Somebody hacked AdBlockPlus because it enabled us to get rid of those annoying ads???

Oohh, just forgot to mention: I am using Mageia 2 !

[oj]

I also had to disable adblock plus on an up to date Mageia 2 system. Firefox locked up on start, so I killed it. When I started it again I got the option of restoring the prior session or starting a new one. To test I selected restore, and it crashed. At that point it showed 2 tabs it was attempting to restore, Duck Duck Go and a page with a web cam that had been open. Those were the only 2 showing.

After I killed again and restarted I selected to start a new session. It opened fine, with the home page (Duck Duck Go) but also another tab that opened itself: an announcement that the flashgot, or download helper add-on (can't remember which, but one of the two) had been updated.

Obviously that page had been scheduled to pop up before the 2 times I killed FF, as nothing would have been installed in the interim. I'm wondering if this sort of 'manufacturer's' page is the culprit behind adblock plus crashing FF. Note that when I got the 'restore or new session' option both time there was no mention that it was going to open the "your add-on has been updated" page. It was lurking scheduled in the background somehow, in a fashion that my preference for startup (restore previous tabs) was unaware.

Something to ponder perhaps. When I get a chance I'll re-enable adblock on that machine and see how it behaves.

[schnuck68]

Hi oj,

In the meantime I have been able to recover the FF profile, which had this crashing behaviour.
If I click on the addon manager quick enough and then disable adblock plus everything is working again.
This took me 10 or 12 tries before I was fast enough. But now (diabled adblock) everything works again.
Should be a bug within adblock plus.

[doktor5000]

If I click on the addon manager quick enough and then disable adblock plus everything is working again.
This took me 10 or 12 tries before I was fast enough.

Just start firefox in safe mode:
http://kb.mozillazine.org/Safe_Mode#Linux

[sglafata]

Issue still exists with the latest Firefox update. When I get a chance, I will downgrade AdBlock Plus to AdBlock, but I do not feel this is the issue. But I digress..... I will try tomorrow as I am unable to today.

Again, this was not a problem for me up to Firefox 10.0.9 release. This started happening after the 10.0.10 release upgrade.

[saptech]

Adblock Plus 2.2.1 & Firefox v17 ESR and no problems at all. Running M3A2 originally. I've ran FF with AP for years under linux and never had any issues.

[sglafata]

I removed AdBlock Plus from Firefox, and installed Adblock (as I find this is essential) and the issue still occurs. I have also found that this issue has occurred twice since I switched from Firefox to Chromium browser. Chromium seems to handle the problem much better than Firefox. Still, the problem exists. I have checked my .xsession-errors log and I get messages that state 'Gdk Warning: XID Collision, Trouble Ahead". Not sure if this is related, but with my desktop hanging on me, i have a suspicious feeling that the problem is related to X. It's just that I can actually function using Chromium, where if I use Firefox, it doesn't take long for the whole thing to crap out on me.

[doktor5000]

How many read the hint to the workaround in the aformentioned bug report? FWIW, there's now even an Errata entry for this: https://wiki.mageia.org/en/Mageia_2_Err ... nd_Adblock

[hintzy64]

Haven't tried it yet since I primarily use Chrome, but I saw it mentioned in that bug report above. Good idea to include it in the Errata.

[schnuck68]

How many read the hint to the workaround in the aformentioned bug report? FWIW, there's now even an Errata entry for this: https://wiki.mageia.org/en/Mageia_2_Err ... nd_Adblock

This link actually cured the reoccuring problem for me. Basically did the following:

Code: Select all

rpm -e --nodeps lib64proxy-mozjs-0.4.7-6.mga2
urpmi lib64proxy-webkit


Thank you for the link!

[schwim]

Mageia Cauldron with all updates:

rpm -e --nodeps lib64proxy-mozjs-0.4.7-6.mga2

Results in:

error: package lib32proxy-mozjs-0.4.7-6.mga2 is not installed

I've searched the packages looking for mozjs and have only found:

libmozjs185_1.0 - JavaScript engine library​ 
JavaScript is the Netscape-developed object scripting languages. This package has been created for purposes of Sablotron and is suitable for embedding in applications. See http://www.mozilla.org/js for details and sources.

Version: 1:1.85-4.mga3
Currently installed version: 1:1.85-4.mga3
Group: System/Libraries
Architecture: i586
Size: 3370 KB
Medium: None (installed)

Any idea on what I might need to change to apply this fix as well?

[isadora]

Mageia Cauldron with all updates:

rpm -e --nodeps lib64proxy-mozjs-0.4.7-6.mga2

Results in:

error: package lib32proxy-mozjs-0.4.7-6.mga2 is not installed

................

Should be:

Code: Select all

rpm -e --nodeps lib64proxy-mozjs-0.4.7-6.1.mga2