Bug 214450

Summary: www/chromium: Segfault when visiting kickstarter.com
Product: Ports & Packages Reporter: Ori Bernstein <ori>
Component: Individual Port(s)Assignee: freebsd-chromium (Nobody) <chromium>
Status: Closed DUPLICATE    
Severity: Affects Some People CC: clutton, cpm, jonc, ws
Priority: --- Flags: bugzilla: maintainer-feedback? (chromium)
Version: Latest   
Hardware: Any   
OS: Any   

Description Ori Bernstein 2016-11-12 18:12:39 UTC 
As initially filed on github: visiting kickstarter.com will reliably segfault the entire Chromium browser (ie, this kills all windows, not just a single tab). This seems to be a persistent issue on all versions from 51.0.2704.84 to 54.0.2840.90. At least one other person has reproduced.

Unfortunately, I don't seem to be able to build with debug information, so I can't give a backtrace. If anyone can give me a hand with extracting better debug information, I'd be glad to take some time to work on it.
Comment 1 clutton 2016-11-12 20:52:25 UTC 
Sure, more hands, better results.

Full debug wouldn't build because we have to many assert() which wouldn't pass.
Fixing unittests would help.

For now, edit args.gn 
Run "make configure" go to your workdir/.../out/Release
and edit args.gn

#is_debug = false
#symbol_level = 0
#remove_webcore_debug_symbols = true

Before starting, make sure you have enough time and computing power.
Comment 2 Ori Bernstein 2016-11-12 22:02:43 UTC 
Currently that's failing for me: 

[4/15486] python "/usr/home/ori/src/ports/freebsd-chromium/www/chromium/work/chromium-54.0.2840.100/build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" --nm="llvm-nm39"  --sofile="./libwtf.so" --tocfile="./libwtf.so.TOC" --output="./libwtf.so" -- clang++39 -shared -Wl,--fatal-warnings -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -fuse-ld=lld -Wl,--icf=all -pthread -m64 -Wl,--export-dynamic -L/usr/local/lib -o "./libwtf.so" -Wl,-soname="libwtf.so" @"./libwtf.so.rsp"
FAILED: libwtf.so libwtf.so.TOC
python "/usr/home/ori/src/ports/freebsd-chromium/www/chromium/work/chromium-54.0.2840.100/build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" --nm="llvm-nm39"  --sofile="./libwtf.so" --tocfile="./libwtf.so.TOC" --output="./libwtf.so" -- clang++39 -shared -Wl,--fatal-warnings -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -fuse-ld=lld -Wl,--icf=all -pthread -m64 -Wl,--export-dynamic -L/usr/local/lib -o "./libwtf.so" -Wl,-soname="libwtf.so" @"./libwtf.so.rsp"
undefined symbol: backtrace in obj/third_party/WebKit/Source/wtf/wtf/Assertions.o

It seems we may be missing an `-lexecinfo` flag somewhere?
Comment 3 clutton 2016-11-12 23:09:32 UTC 
Join maillist, we discuss things there.

Yes, -lexecinfo would do, but more importantly, what target do you build?
This is a bug tracker IMHO, about development/etc discuss things on maillist.
Comment 4 Ori Bernstein 2016-11-19 07:51:26 UTC 
Ok, moving to the freebsd-chromium mailing list, at least to figure out why exactly I'm getting build failures, and how to fix those.

(Sorry for the delay; had a busy week.)
Comment 5 Jonathan Chen 2016-11-23 18:39:34 UTC 
The issue still exists with chromium 54.x. Visiting kickstarter.com will take down chromium hard.
Comment 6 Wayne Sierke 2016-11-24 04:43:34 UTC 
(In reply to Ori Bernstein from comment #0)
Note that this started for me with an upgrade to 48.0.2564.103 - see bug #207298, comment #1

Reverting to the previously installed chromium package didn't resolve it suggesting that the problem might be tied in with one of the dependencies. (At that time I was visiting kickstarter.com reasonably often.)
Comment 7 Carlos J. Puga Medina freebsd_committer freebsd_triage 2017-02-02 13:06:55 UTC 

*** This bug has been marked as a duplicate of bug 207298 ***