The full cause of this chromium crash on 32 bit linux (while the corresponding google-chrome-stable version worked fine) was found as issue 439795 on https://code.google.com/p/chromium/
It was caused by including a check for error codes for non-existent system calls that is not in chromium; see below. This issue is in the debian 3.14 kernel and has been fixed in the 3.16 kernel. The full details are in the link below and comment 50 (below) summarizes the issue. thanks, --jack https://code.google.com/p/chromium/issues/detail?can=2&start=0#=100&q=&colspec=ID%20Pri%20M%20Week%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&id=439795 #50 ric...@chromium.org Hm, I'm not sure why chromium 39.0.2171.71 would include the new syscall check. From what what I can tell, that version does not have the check for the seccomp syscall: https://chromium.googlesource.com/chromium/src.git/+/39.0.2171.71/sandbox/linux/seccomp-bpf/sandbox_bpf.cc Compare that to https://chromium.googlesource.com/chromium/src.git/+/master/sandbox/linux/seccomp-bpf/sandbox_bpf.cc, which has the KernelSupportsSeccompTsync function. You'd probably need to check with whoever built the package you're using to figure out how it managed to include that code. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
