Chromium 18.0.1025.151 segfaults a lot

sardaukar · 2012-04-06 13:15:08

Hey, guys.

Am I the only one noticing that the newest Chromium beta segfaults every 5 minutes? Does anyone know what can be causing this?

My uname -a:

Linux beast 3.2.13-1-ARCH #1 SMP PREEMPT Sat Mar 24 09:10:39 CET 2012 x86_64 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux

Thanks for any pointers!

Weegee · 2012-04-06 13:39:27

No, you're not the only one, I'm also noticing it. However I have no idea how to find out why it segfaults, thus I've started Chromium from the terminal - now let's see.

sardaukar · 2012-04-06 13:51:15

I started it too - it just says 'Segmentation fault'. Example:

[bruno@beast betribes (master)]$ chromium
[26676:26687:364438855004:ERROR:object_proxy.cc(239)] Failed to call method: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Segmentation fault

The last line is the only feedback, the other lines before it always show up on every console launch.

Last edited by sardaukar (2012-04-06 13:51:38)

skwo · 2012-04-06 14:32:22

Same Issue here

Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Segmentation fault

Then chromium crashes.

The funny thing is that I dont even have Nvidia GPU, I am using Dell Latitude E5410 laptop with Intel GPU in it.

I think downgrading is what I'm going to do.

faulty · 2012-04-06 15:25:04

Yep, getting random segfaults too. Archlinux x64

Last edited by faulty (2012-04-06 15:25:33)

anta40 · 2012-04-06 15:28:05

Yeah, experiencing random crashes here.
If I open lots of tabs, chromium crashes in < 3 minutes.
But if I don't open any tab, chromium goes fine.

Weird.

MadCat_X · 2012-04-06 15:28:07

You can try installing "libvdpau" from extra if you don't have it already. I have an nVidia GPU with proprietary drivers and libvdpau installed and I'm getting a different error on segfault. Dmesg gives me

Chrome_HistoryT[1813] general protection ip:7f272fae1127 sp:7f27147362b0 error:0 in chromium[7f272e33d000+43c6000]

I downgraded to 142 which had been working fine.

lost eden · 2012-04-06 15:38:26

I've been getting frequent segfaults too since updating this morning, happens when I open a new tab & start typing in the address bar. It's been behaving for the past 20 minutes or so though...

MadCat_X · 2012-04-06 15:50:38

lost eden wrote:

I've been getting frequent segfaults too since updating this morning, happens when I open a new tab & start typing in the address bar. It's been behaving for the past 20 minutes or so though...

That's pretty much what I've been experiencing. It's kinda interesting that 142 had been freezing under these circumstances until I uninstalled libcanberra-pulse.

lost eden · 2012-04-06 15:53:33

I don't know whether it is relevant, but before updating to 151 this morning my install would sometimes segfault right when I tried to run it; I would do [alt]+[f2] & enter Chromium & seemingly nothing would happen, until I tried running it in a terminal & saw that it was just segfaulting. It would always start successfully after a few attempts though.

Svenstaro · 2012-04-06 18:45:51

Also check our bug report and report results or hints. https://bugs.archlinux.org/task/29309

Also go bug the chromium project.

shomyo · 2012-04-07 06:17:55

yeah, random crash after starts typing into the omnibox =/

starnostar · 2012-04-07 07:19:38

completley fixed my crashing issues that (much like others here) got even worse with the last update

go to about:flags and disable everything (as I haven't pinpointed which one is causing the segfaults), my guess is one utilizing gpu-accel...for whatever reason some of these came turned on by default (as I didn't turn them on)

EDIT: Nevermind, everything was back to normal for a good 2 hours, now its acting up again...sigh

Last edited by starnostar (2012-04-07 07:36:23)

donniezazen · 2012-04-07 07:45:51

It have been noticing it for past few hours.

phoric · 2012-04-07 08:12:41

Same here, after updating to 18.0.1025.151 this morning. Hard crash on typing in the address bar, several times per day (never before had a Chromium crash like this).

Lowra · 2012-04-07 09:13:19

Me too, since I updated to 18.0.1025.151. Random crashes while opening a new tab, and typing something in the omnibar apparently

DarksideEE7 · 2012-04-07 11:27:02

Same here, just updated about 10 minutes ago and I've already experienced 5 crashes. Running x86_64 with no testing. Haven't tested on my desktop yet. For me it's crashing when I open a new tab and begin typing the URL.

I have Adblock experimental installed with experimental APIs enabled in about:flags, however it hasn't caused any problems before...
Since it mentions Chrome_HistoryT I tried to reproduce in incognito mode.....I can't get it to crash. I cleared history, data, everything for all time and was able to reproduce instantly.
dmesg's output after a few crashes:

[  276.855172] Chrome_HistoryT[1873] general protection ip:7ff53e8fa127 sp:7ff524dab2b0 error:0 in chromium[7ff53d156000+43c6000]
[  300.395088] Chrome_HistoryT[2382] general protection ip:7f437abd8127 sp:7f43610bf2b0 error:0 in chromium[7f4379434000+43c6000]
[  313.559888] Chrome_HistoryT[2587] general protection ip:7f53a6277127 sp:7f538c7542b0 error:0 in chromium[7f53a4ad3000+43c6000]
[  590.787548] Chrome_HistoryT[2771] general protection ip:7fbade55c127 sp:7fbac4a902b0 error:0 in chromium[7fbadcdb8000+43c6000]
[  607.320815] Chrome_HistoryT[3127] general protection ip:7fc49b396127 sp:7fc4810332b0 error:0 in chromium[7fc499bf2000+43c6000]
[  679.106383] Chrome_HistoryT[3295] general protection ip:7f7799c86127 sp:7f778016d2b0 error:0 in chromium[7f77984e2000+43c6000]
[  758.759866] Chrome_HistoryT[3915] general protection ip:7fd3601e5127 sp:7fd3469662b0 error:0 in chromium[7fd35ea41000+43c6000]
[  808.598623] Chrome_HistoryT[4325] general protection ip:7f5b03560127 sp:7f5ae9a3c2b0 error:0 in chromium[7f5b01dbc000+43c6000]
[  876.832539] Chrome_HistoryT[4490] general protection ip:7f94baf56127 sp:7f94a14322b0 error:0 in chromium[7f94b97b2000+43c6000]
[  896.514948] Chrome_HistoryT[4738] general protection ip:7faa4ee52127 sp:7faa35acf2b0 error:0 in chromium[7faa4d6ae000+43c6000]

Last edited by DarksideEE7 (2012-04-07 11:39:44)

skython · 2012-04-07 15:42:03

Some people experienced flash problems with chromium and libvdpau and solved it by setting

export VDPAU_NVIDIA_NO_OVERLAY=1

in .xinitrc and restarting X.

I did the same and haven't yet experienced any segfault anymore.
Still testing, I'll update this post if it crashes again.

Edit:
Still crashing

Last edited by skython (2012-04-07 15:57:14)

n0dl · 2012-04-07 15:52:06

*slight sigh of relief* Oh man I thought there was something wrong with my new computer and/or fresh install. Anyhow I'm having the same problem. Probably going to use ff for a bit to see if the problem gets resolved at some later time. For now here's a copy of my dmesg output

[ 3680.313152] Chrome_HistoryT[703] general protection ip:7f43b4cd7127 sp:7f43a14952b0 error:0 in chromium[7f43b3533000+43c6000]
[ 3905.659586] Chrome_HistoryT[6220] general protection ip:7f184862c127 sp:7f1834dd50b0 error:0 in chromium[7f1846e88000+43c6000]
[ 4106.225406] Chrome_HistoryT[8207] general protection ip:7fc2061aa127 sp:7fc1f29592b0 error:0 in chromium[7fc204a06000+43c6000]
[ 4160.528369] Chrome_HistoryT[17588] general protection ip:7f08f443c127 sp:7f08e0c582b0 error:0 in chromium[7f08f2c98000+43c6000]
[ 4237.936965] Chrome_HistoryT[17686] general protection ip:7f2bc2110127 sp:7f2bae8aa2b0 error:0 in chromium[7f2bc096c000+43c6000]
[ 4256.312234] Chrome_HistoryT[17777] general protection ip:7f9fab496127 sp:7f9f9742f2b0 error:0 in chromium[7f9fa9cf2000+43c6000]
[ 4503.746925] Chrome_HistoryT[17844] general protection ip:7f90edbaa127 sp:7f90d9bc52b0 error:0 in chromium[7f90ec406000+43c6000]
[ 5220.398582] Chrome_HistoryT[18219] general protection ip:7fdf0664e127 sp:7fdef26690b0 error:0 in chromium[7fdf04eaa000+43c6000]

ill try to see if I can get some strace output as well...

djiit · 2012-04-07 16:59:18

Hi,

Same here... (just to inform that you're not alone )

BR,

hjl3 · 2012-04-07 17:23:33

I implemented a work around that seems to have worked so far. Firstly, install libvdpau (Nvidia VDPAU library), even if you don't use the nvidia kernel module (or nvidia card for that matter).

pacman -S libvdpau

Then create a symlink for libvdpau.so to libvdpau_nvidia.so.

cd /usr/lib
ln -s libvdpau.so libvdpau_nvidia.so

Chromium no longer segfaults, but does occasionally spit out the following error (without crashing).

/usr/lib/libvdpau.so: undefined symbol: vdp_imp_device_create_x11

Edit: Nevermind, just has a Seg fault

Last edited by hjl3 (2012-04-07 17:54:43)

victorphb · 2012-04-07 18:36:51

Same problem here, after upgrade to 18.0.1025.151, when I starts typing into the omnibox

kelloco2 · 2012-04-07 18:40:40

Same here. I have tried several things but without success. First flashplugin, now chromium - I downgraded to version 17.0.963.83 and pin it (/etc/pacman.conf). nvidia 295.33-1

delcypher · 2012-04-07 19:22:25

Another Arch user has reported this issue upstream http://code.google.com/p/chromium/issue … ?id=122525.

For now I've just downgraded to 18.0.1025.142 by doing

# pacman -U /var/cache/pacman/pkg/chromium-18.0.1025.142-1-x86_64.pkg.tar.xz

This'll work fine if you haven't cleaned up your cache in a while like I have

Last edited by delcypher (2012-04-07 19:23:01)

kelloco2 · 2012-04-07 19:38:56

If you cleaned up your cache;
https://wiki.archlinux.org/index.php/Do … g_Packages
easy and working

Arch Linux

#1 2012-04-06 13:15:08

Chromium 18.0.1025.151 segfaults a lot

#2 2012-04-06 13:39:27

Re: Chromium 18.0.1025.151 segfaults a lot

#3 2012-04-06 13:51:15

Re: Chromium 18.0.1025.151 segfaults a lot

#4 2012-04-06 14:32:22

Re: Chromium 18.0.1025.151 segfaults a lot

#5 2012-04-06 15:25:04

Re: Chromium 18.0.1025.151 segfaults a lot

#6 2012-04-06 15:28:05

Re: Chromium 18.0.1025.151 segfaults a lot

#7 2012-04-06 15:28:07

Re: Chromium 18.0.1025.151 segfaults a lot

#8 2012-04-06 15:38:26

Re: Chromium 18.0.1025.151 segfaults a lot

#9 2012-04-06 15:50:38

Re: Chromium 18.0.1025.151 segfaults a lot

#10 2012-04-06 15:53:33

Re: Chromium 18.0.1025.151 segfaults a lot

#11 2012-04-06 18:45:51

Re: Chromium 18.0.1025.151 segfaults a lot

#12 2012-04-07 06:17:55

Re: Chromium 18.0.1025.151 segfaults a lot

#13 2012-04-07 07:19:38

Re: Chromium 18.0.1025.151 segfaults a lot

#14 2012-04-07 07:45:51

Re: Chromium 18.0.1025.151 segfaults a lot

#15 2012-04-07 08:12:41

Re: Chromium 18.0.1025.151 segfaults a lot

#16 2012-04-07 09:13:19

Re: Chromium 18.0.1025.151 segfaults a lot

#17 2012-04-07 11:27:02

Re: Chromium 18.0.1025.151 segfaults a lot

#18 2012-04-07 15:42:03

Re: Chromium 18.0.1025.151 segfaults a lot

#19 2012-04-07 15:52:06

Re: Chromium 18.0.1025.151 segfaults a lot

#20 2012-04-07 16:59:18

Re: Chromium 18.0.1025.151 segfaults a lot

#21 2012-04-07 17:23:33

Re: Chromium 18.0.1025.151 segfaults a lot

#22 2012-04-07 18:36:51

Re: Chromium 18.0.1025.151 segfaults a lot

#23 2012-04-07 18:40:40

Re: Chromium 18.0.1025.151 segfaults a lot

#24 2012-04-07 19:22:25

Re: Chromium 18.0.1025.151 segfaults a lot

#25 2012-04-07 19:38:56

Re: Chromium 18.0.1025.151 segfaults a lot

Board footer