Closed
Bug 1142646
Opened 9 years ago
Closed 9 years ago
Crash when visiting a website with Adblock Plus enabled
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: toriningen.me+bugzilla-ruby, Unassigned)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 20150305021524 Steps to reproduce: 1. Create fresh profile 2. Install Adblock Plus 2.6.8 3. Visit "http://half-life3.com" Actual results: Firefox crashes, Nightly as well, despite the e10s status. Expected results: Website should just open and show uninteresting domain parking page.
So, after few hours of instruction-by-instruction tracing I was finally able to find the reason of crash. It was induced by homebrew. After installing `xulrunner` via homebrew, there were `nss` and `nspr` packages symlinked into `/usr/local/lib`. For some reason Firefox dynamic linker picked them up TOGETHER with same libraries at the build directory. Spotted this accidentally when I noticed base addresses differ for what I'm stepping through, and that module loader shows there are two instances of library loaded at different paths. To fix crash, do the following at the shell: $ homebrew unlink nspr nss
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Comment 3•9 years ago
|
||
Wow. Well spotted!
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → WORKSFORME
Comment 4•9 years ago
|
||
Soliciting the opinion of our low-level experts - is this something that is FF's fault, or should it be resolved on the end of the Homebrew folks?
Flags: needinfo?(mh+mozilla)
Comment 5•9 years ago
|
||
Will followup in the other bug.
Updated•9 years ago
|
Flags: needinfo?(mh+mozilla)
Comment 6•9 years ago
|
||
I think it's ABP who's trying to open the nss from homebrew: https://hg.adblockplus.org/adblockplus/file/2.6.8/lib/utils.js#l620 It is kinda related to bug 593484 again.
You need to log in
before you can comment on or make changes to this bug.
Description
•