google-chrome segfaults on Slackware64 -current

budman85 · 05-24-2012, 09:42 PM

Quote:

Originally Posted by TL_CLD

When I start google-chrome with strace, it dies with this:

Code:

write(43, "\0", 1)                      = 1
write(43, "\0", 1)                      = 1
write(33, "\0", 1)                      = 1
write(43, "\0", 1)                      = 1
write(43, "\0", 1)                      = 1
write(43, "\0", 1)                      = 1
write(33, "\0", 1)                      = 1
write(43, "\0", 1)                      = 1
+++ killed by SIGSEGV +++
Segmentation fault

Without strace I simply get:

Code:

[2:2:952748919:ERROR:nacl_fork_delegate_linux.cc(106)] Bad NaCl helper startup ack (0 bytes)
Segmentation fault

The WM used does not appear to matter. I've tried KDE, XFCE and xmonad.

This happens consistently on two different systems: A Lenovo T420 laptop and a Sun Ultra27 workstation.

It is driving me nuts.

I've tried deleting .config/google-chrome, to no avail. I'm currently running the latest google-chrome 19.something.

I saw a thread under ArchLinux. They found it was because the nscd daemon is no longer running. The quick work around is to run the daemon again, remember to create the dirs /var/run/nscd and /var/db/nscd before starting.

The real problem has been fixed in glibc 2.15.5 - current is using 2.15.2. I sent Patrick a note about this.

here is a link to the article https://bbs.archlinux.org/viewtopic.php?id=133021

ruario · 05-25-2012, 12:21 AM

@TL_CLD: You have installed the other dependencies from /extra right (google-chrome-pam-solibs, GConf and ORBit2)?

TL_CLD · 05-25-2012, 02:21 AM

Quote:

Originally Posted by ruario

@TL_CLD: You have installed the other dependencies from /extra right (google-chrome-pam-solibs, GConf and ORBit2)?

Yes. I've got all three. Note that Google Chrome is working, it just takes 10-15 crashes during startup before it finally stays alive. Once it is running, it is rock solid.

TL_CLD · 05-25-2012, 02:35 AM

Quote:

Originally Posted by budman85

I saw a thread under ArchLinux. They found it was because the nscd daemon is no longer running. The quick work around is to run the daemon again, remember to create the dirs /var/run/nscd and /var/db/nscd before starting.

The real problem has been fixed in glibc 2.15.5 - current is using 2.15.2. I sent Patrick a note about this.

here is a link to the article https://bbs.archlinux.org/viewtopic.php?id=133021

So if/when Pat updates glibc to 2.15.5 the problem will hopefully go away. That is good to know.

I've no scripts for nscd in /etc/rc.d/ so I'll just leave that as is and hope for the glibc fix. I don't want to muck around too much with -current.

budman85 · 05-25-2012, 07:26 AM

Quote:

Originally Posted by ruario

@TL_CLD: You have installed the other dependencies from /extra right (google-chrome-pam-solibs, GConf and ORBit2)?

I checked when the packages were installed, the glibc upgrade was in April.
I was using Chrome 16.0.912 without issue.
When I upgraded to Chrome 18.0.1025, the segfaults were continuous.
I saw some notes on Google Chrome dev forums about them making glib 2.18 the minimum version.
Maybe this has some residuals. glib2 2.28.6 was recently added.

When I check ldd /opt/google/chrome/chrome I only see one lib that is not from lib64 dir
linux-vdso.so.1 (0x00007fff287ff000)

I will try downgrading to version 16 to see if that segfaults on startup.

volkerdi · 05-25-2012, 10:25 AM

Hello, glibc-2.15 is the latest, and there is no such thing as glibc-2.15.5. The Arch bug report refers to their patched package, glibc-2.15-5.

This is the actual location to get the patch:

http://sourceware.org/bugzilla/show_bug.cgi?id=13594

budman85 · 05-26-2012, 12:59 AM

Quote:

Originally Posted by volkerdi

Hello, glibc-2.15 is the latest, and there is no such thing as glibc-2.15.5. The Arch bug report refers to their patched package, glibc-2.15-5.

This is the actual location to get the patch:

http://sourceware.org/bugzilla/show_bug.cgi?id=13594

Thanks.

I rebooted the system today, same segfault.
This time strace showed it trying to read the cache dir.

~/.cache/google-chrome

I renamed the dir and it loaded with no segfault.

willysr · 05-26-2012, 02:14 AM

Pat has updated glibc with the patch mentioned above
can you confirmed that the patch work or does not work?

budman85 · 05-26-2012, 06:07 PM

Quote:

Originally Posted by willysr

Pat has updated glibc with the patch mentioned above
can you confirmed that the patch work or does not work?

downloading now - will try in a few - thanks

Nice! No more segfault!

I rebooted, chrome loaded right up.

The reoccurring issue was:
Reboot
start - segfault
restart - runs fine, close it
restart - segfault
restart - runs fine, close it
restart - segfault
and so on..

After update, I tried the same steps:
Reboot
start - ran fine, close it
restart - ran fine, close it
and so on...

Looks like the patch worked.

Tell Pat thanks!

Also, tell him thanks for upgrading xscreensaver to 5.15, that fixes a hard crash bug for newer Nvidia cards and prop. divers.

Rich

TL_CLD · 05-27-2012, 02:24 AM

The latest glibc -current update fixes it completely. It works flawlessly on both my computers now. Thank you!

willysr · 05-27-2012, 04:22 AM

Quote:

Originally Posted by budman85

Tell Pat thanks!

Also, tell him thanks for upgrading xscreensaver to 5.15, that fixes a hard crash bug for newer Nvidia cards and prop. divers.
Rich

You can thank him directly via his email

TL_CLD · 05-27-2012, 10:13 AM

He's also on Google+

https://plus.google.com/u/0/114480574919795916970/posts