Arch Linux

dgs

Member

Registered: 2018-05-11

Posts: 15

[SOLVED] VLC/MPV/Chrome - Segmentation fault under user, not root

Hi all,

Recently I started getting segmentation faults under my own user when running certain applications. I first noticed it with MPV when trying to playback a video. I then tried VLC, and got the same issue. Eventually I started noticing it with other apps, like Steam and Chrome.

MPV, VLC and Steam all report to libglc-2.28.so via dmesg, as shown in the output below. This error does not occur when running these apps under different users, like say root. I even made a new user on my machine to test this, and it also had no problems running any of these, so my guess is that it's my user configuration somehow.

MPV:

Playing: Videos/FPGA/FPGAs and VHDL- Part 1 - What is an FPGA + Program
 (+) Video --vid=1 (*) (h264 1920x1080 50.000fps)
 (+) Audio --aid=1 --alang=eng (*) (opus 2ch 48000Hz)
Segmentation fault (core dumped)

dmesg output regarding segfault for mpv:

[  446.376350] mpv/vo[2451]: segfault at 7fcbcc339ff0 ip 00007fcbda743a6e sp 00007fcbcc339ff0 error 6 in libc-2.28.so[7fcbda6e2000+14b000]

VLC with VLC_VERBOSE environment variable set to 3(debug):

[00007f05dc10c430] main generic debug: using hw decoder module "vdpau_avcodec"
[00007f05d4c0b930] avcodec decoder: Using NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT 2019 for hardware decoding
[00007f05d4c0b930] main decoder debug: Received first picture
[00007f05e8000c40] main input debug: Decoder wait done in 384 ms
[0000557320434790] pulse audio output debug: cannot synchronize start
[0000557320434790] pulse audio output debug: deferring start (24304 us)
[0000557320434790] pulse audio output debug: deferring start (4501 us)
[0000557320434790] pulse audio output warning: starting late (-15703 us)
[0000557320434790] pulse audio output debug: started
[0000557320434790] pulse audio output debug: changing sink 0: alsa_output.pci-0000_00_1f.3.analog-stereo (Built-in Audio Analog Stereo)
[0000557320466280] qt interface debug: Logical video size: 1920x1080
[00007f05dc0c86e0] main window debug: resized to 1920x1080
[00007f05c0001370] main vout display debug: VoutDisplayEvent 'resize' 1920x1080
[00007f05dc0c86e0] main window debug: resized to 724x874
[00007f05c0001370] main vout display debug: VoutDisplayEvent 'resize' 724x874
[00007f05dc001530] main video output warning: picture is too late to be displayed (missing 33 ms)
[00007f05dc001530] main video output warning: picture is too late to be displayed (missing 13 ms)
[00007f05c0001370] main vout display debug: auto hiding mouse cursor
Segmentation fault (core dumped)

dmesg output for VLC:

[  686.937041] vlc[2956]: segfault at 7f060311ffc0 ip 00007f061e4a9a6e sp 00007f060311ffc0 error 6 in libc-2.28.so[7f061e448000+14b000]

Both steam and Chromium only report segmentation fault(core dumped), but dmesg reports the following:
Steam:

[  806.405778] steam[3589]: segfault at ff770ffc ip 00000000f7a3a87a sp 00000000ff770fd0 error 6 in libc-2.28.so[f79d9000+14f000]

Chromium:

[  856.072742] chromium[3757]: segfault at 7ffeca010f98 ip 000055bebe5710b3 sp 00007ffeca010fa0 error 6 in chromium[55beb7f20000+6653000]

I've already tried to reinstall glibc and see if this was the issue since it was recently updated, but this did not help. I also tried to downgrade glibc, also with no luck. I tried this before noticing this issue did not happen on other users, which makes me think it's my user configuration, somehow.

Could anyone shed some light on this, or have any ideas/suggestions?

Thanks!

Last edited by dgs (2019-04-20 15:55:28)

Zod

Member

From: Hoosiertucky

Registered: 2019-03-10

Posts: 629

Re: [SOLVED] VLC/MPV/Chrome - Segmentation fault under user, not root

I don't know, just spitballing here...could it be your user permissions to a common working directory like /tmp or /var/tmp?

Edit: getting rid of dumb speculation.

Last edited by Zod (2019-04-20 14:13:56)

xerxes_

Member

Registered: 2018-04-29

Posts: 675

Re: [SOLVED] VLC/MPV/Chrome - Segmentation fault under user, not root

Try delete crashing programs configuration files (vlc (.config/vlc/ .local/share/vlc/), mpv (.config/mpv/ ), chromium (.config/chromium/ .cache/chromium/)), so when you run them next time, they will start with default settings and recreate default configuration files.

Last edited by xerxes_ (2019-04-20 14:26:43)

seth

Member

Registered: 2012-09-03

Posts: 51,056

Re: [SOLVED] VLC/MPV/Chrome - Segmentation fault under user, not root

Instead of looking at the kernel ringbuffer for userspace crashes, look at the actual coredumps to see what happens before tapping in libc?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

dgs

Member

Registered: 2018-05-11

Posts: 15

Re: [SOLVED] VLC/MPV/Chrome - Segmentation fault under user, not root

I don't know, just spitballing here...could it be your user permissions to a common working directory like /tmp or /var/tmp?

Edit: getting rid of dumb speculation.

Try delete crashing programs configuration files (vlc (.config/vlc/ .local/share/vlc/), mpv (.config/mpv/ ), chromium (.config/chromium/ .cache/chromium/)), so when you run them next time, they will start with default settings and recreate default configuration files.

Instead of looking at the kernel ringbuffer for userspace crashes, look at the actual coredumps to see what happens before tapping in libc?

Thanks for the suggestions guys. 

After reverting some system modifications I made, I realized that changing my cursor theme back to the original fixed the segfaults. I had changed my cursor via the gtk config file in ~/.config/gtk-3.0. Reverting it to the default or to a different one got rid of the segfaults.

The weird thing is, this same cursor theme works just fine on 2 other machines with the same exact system configuration. They all pull the configs from the same repository. The only difference between them is the hardware.
Strange.

Anyway, thank you guys for the suggestions. I will see if I can figure out how is this theme related to the segmentation faults. I'll mark this as solved in the meantime.