Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35933 - Segmentation Fault in Chromium starting

Attached to Project: Arch Linux
Opened by Jose M Rodriguez (foxaxel) - Tuesday, 25 June 2013, 20:45 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 27 June 2013, 05:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

At least for 2 versions Chromium is failing to start due to Segmentation Fault.

I was waiting for this error to solve by an update. It started to fail after the "pacman -Syu" when the libraries were moved from /lib to /usr/lib.

The output is quite simple:

$ chromium
Segmentation fault (core dumped)

dmesg sais:

[ 6096.150263] systemd-journald[123]: Failed to write entry, ignoring: Argument list too long

I have attached the strace output and gdb backtrace.

Additional info:

* chromium package version: 28.0.1500.52-1
* nss package version: 3.14.3-3


Thanks
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Thursday, 27 June 2013, 05:23 GMT
Reason for closing:  Works for me
Comment by Jose M Rodriguez (foxaxel) - Tuesday, 25 June 2013, 20:52 GMT
Sorry, I clicked the wrong button. Here are the attachements.

And, of course, the line from dmesg is not that one, is this:

[ 6471.922636] Chrome_IOThread[5144]: segfault at 68 ip 00007fdb34f24f93 sp 00007fdb1e3e2c08 error 6 in libnss3.so[7fdb34ed2000+136000]

Thanks you.
   strace.log (204.2 KiB)
   gdb.log (3.6 KiB)
Comment by Bogomil (smirky) - Wednesday, 26 June 2013, 07:51 GMT
I use Chromium 27.0.1453.110
All the version above so far give me problems. For example, the picture frames in facebook freeze the tab and a few more things :|
Comment by Evangelos Foutras (foutrelis) - Thursday, 27 June 2013, 05:22 GMT
The /usr/lib move happened a year ago; it's a bit too late to attempt to troubleshoot this.

Also the strace log you attached is of google-chrome, which indicates that it's not a Chromium packaging issue.

For the freezes that are specific to Chromium 28, there's  FS#35856 .

Loading...