531844 - Adblock plus crashes firefox 3.6b4 on Ubuntu Linux x64

Status: RESOLVED WORKSFORME

(Firefox :: Extension Compatibility, defect)

Description

[william]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4

In Firefox 3.6b4, when I install Adblock Plus 1.1.1 and start the browser with one of the startup tabs having blocked ads, Firefox crashes.

Reproducible: Always

Steps to Reproduce:
1. Create 64bit VirtualBox machine
2. Install 64bit Ubuntu desktop
3. Install ia32libs (& deps)
4. Download 32bit Firefox 3.6b4 from mozilla.com
5. Install adblock plus 1.1.1
6. Enable usa easylist
7. Go to www.smashingmagazine.com or some other page with ads
8. Close firefox
9. Open firefox, smashingmagazine should be the page that loads.
Actual Results:  
Firefox crashes

Expected Results:  
Firefox should open and the ads should be blocked.

I have reproduced this on my normal profile, a clean profile, and even a clean OS in a virtual machine using the steps listed above. I do not know if this happens on a 32bit installation. That could be part of the issue. I am using Ubuntu 9.10 x64. Firefox 3.6b4 32bit binaries from mozilla.com.

I ran Firefox 3.6 betas 1-3 in the same configuration with no problems.

I can upload the VM I used to reproduce this if no one else can reproduce it independently.

I originally reported the bug to the Adblock Plus forums here: https://adblockplus.org/forum/viewtopic.php?f=1&t=4823&p=30698#p30698

Comment 1

[Wladimir Palant]

The crash report is here: http://crash-stats.mozilla.com/report/index/bp-8c156fe9-f27d-4a4a-815d-d2d7a2091129

I have no idea what "No thread was identified as the cause of the crash" means...

Comment 2

[Matthias Versen [:Matti]]

That means that the crashreporter failed to find the crash cause in the dumpfile.
Reporter: Can you please try to generate a new ID ?

It's likely that we get the same result for the new ID and in that case you can only use gdb to get a stack trace.

Comment 3

[william]

You mean crash it again, report the crash and point you to the url?

Comment 4

[william]

If that is the case, here:
http://crash-stats.mozilla.com/report/index/a793293d-25df-4993-9080-436022091130

Comment 5

[Matthias Versen [:Matti]]

Thanks !
the same error with processing the dump file as I already expected :-(
maybe timeless can help with GDB instructions ?

Comment 6

[timeless]

64bit linux? stackwalker doesn't support that iirc.

use a vendor build and see https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report#Linux

Comment 7

[william]

If it helps, when I run firefox in the command line and it crashes, this is the output:

###!!! ABORT: no usable poison region identified: file /builds/moz2_slave/linux_build/build/layout/base/nsPresArena.cpp, line 212
UNKNOWN [./libxul.so +0x003599D6]
PR_CallOnce+0x000000D3 [./libnspr4.so +0x000176A3]
UNKNOWN [./libxul.so +0x00359C81]
UNKNOWN [./libxul.so +0x003598CE]
UNKNOWN [./libxul.so +0x003699D7]
UNKNOWN [./libxul.so +0x00369AF4]
UNKNOWN [./libxul.so +0x004A1BDE]
UNKNOWN [./libxul.so +0x00570666]
UNKNOWN [./libxul.so +0x0034C4F5]
UNKNOWN [./libxul.so +0x0034E489]
UNKNOWN [./libxul.so +0x0034E780]
UNKNOWN [./libxul.so +0x0082621E]
UNKNOWN [./libxul.so +0x008221F3]
UNKNOWN [./libxul.so +0x0082A796]
UNKNOWN [./libxul.so +0x0082BC91]
UNKNOWN [./libxul.so +0x0081C835]
UNKNOWN [./libxul.so +0x00A59427]
UNKNOWN [./libxul.so +0x00A57D1D]
UNKNOWN [./libxul.so +0x005FF542]
UNKNOWN [./libxul.so +0x0062873C]
UNKNOWN [./libxul.so +0x00626245]
UNKNOWN [./libxul.so +0x001E6696]
UNKNOWN [./libmozjs.so +0x000642EB]
UNKNOWN [./libmozjs.so +0x00065BFB]
UNKNOWN [./libmozjs.so +0x00065F15]
UNKNOWN [./libmozjs.so +0x000527B2]
js_Invoke+0x0000056F [./libmozjs.so +0x000596CF]
UNKNOWN [./libxul.so +0x001DC462]
UNKNOWN [./libxul.so +0x001D7643]
UNKNOWN [./libxul.so +0x00A9C495]
UNKNOWN [./libxul.so +0x00A67813]
UNKNOWN [./libxul.so +0x00A67F82]
UNKNOWN [./libxul.so +0x0085227F]
UNKNOWN [./libxul.so +0x008792E7]
UNKNOWN [./libxul.so +0x008796D1]
UNKNOWN [./libxul.so +0x00888821]
UNKNOWN [./libxul.so +0x00851BD6]
UNKNOWN [./libxul.so +0x00851F35]
NS_InvokeByIndex_P+0x0000002F [./libxul.so +0x00A9B97F]
UNKNOWN [./libxul.so +0x001DEBD0]
UNKNOWN [./libxul.so +0x001E4C11]
js_Invoke+0x000003B4 [./libmozjs.so +0x00059514]
UNKNOWN [./libmozjs.so +0x0004F8D8]
js_Invoke+0x0000056F [./libmozjs.so +0x000596CF]
UNKNOWN [./libxul.so +0x001DC462]
UNKNOWN [./libxul.so +0x001D7643]
UNKNOWN [./libxul.so +0x00A9C495]
UNKNOWN [./libxul.so +0x008864F6]
UNKNOWN [./libxul.so +0x00886F3A]
UNKNOWN [./libxul.so +0x008870E9]
XRE_main+0x000024DE [./libxul.so +0x001A9CF0]
UNKNOWN [./firefox-bin +0x000015AA]
__libc_start_main+0x000000E6 [/lib32/libc.so.6 +0x00016B56]

Comment 8

[william]

I am not using vendor packages. I am using the binaries from mozilla.com. I do not believe they have debug symbols. Ubuntu modifies Firefox so heavily as to be useless for debugging, and their betas are pretty much useless.

For me to get a debug build I would need to compile it myself I think. Could I use a nightly?

Comment 9

[timeless]

will: we strip debug symbols from 99% of our builds. There is a script you can try to find to get the symbols, but i have no experience using it.

i'd sooner suggest building yourself. and yeah, i sympathize and appreciate that you don't want to use the ubuntu builds, sometimes they are expedient, and if/when I suggest using them, i will support the person through debugging them, but yeah, generally, it's a bad idea.

Comment 10

[william]

I installed the nightly from ubuntu with debug symbols and adblock works perfectly. It also works perfectly with the nightlies from mozilla.org. I suppose I will just switch to a nightly for the time being and it sounds like it will be fixed in Fx3.6b5.

Thanks for everyone's help. I have never seen a crash report responded to so promptly.

Comment 11

[Matthias Versen [:Matti]]

Thanks for the response, marking wfm