Announcements

Help Wizard

Step 1

NEXT STEP

Spotify binary frequently crashing and dumping core (Ubuntu binary + Snap)

Solved!

Spotify binary frequently crashing and dumping core (Ubuntu binary + Snap)

Hi!

 

The spotify binary frequently dumps core on my Gentoo Linux laptop (x86_64, glibc-2.40, kernel 6.1.119).

 

It seems to only affect some child process, as Spotify itself (main window) keeps running and playing music.

 

Spotify binary (1.2.48, see https://packages.gentoo.org/packages/media-sound/spotify) from Ubuntu repo crashing:

 

2024-11-25 08:56:29 +01:00; zephyr; daemon.info; spotify[1039550]: *** stack smashing detected ***: terminated
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd-coredump[1039588]: Process 1039550 (spotify) of user 20001 terminated abnormally with signal 6/ABRT, processing...
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd[1]: Created slice Slice /system/systemd-coredump.
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd[1]: Started Process Core Dump (PID 1039588/UID 0).
2024-11-25 08:56:29 +01:00; zephyr; daemon.info; systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
2024-11-25 08:56:30 +01:00; zephyr; local0.crit; systemd-coredump[1039589]: Process 1039550 (spotify) of user 20001 dumped core.

[...]

Stack trace of thread 1039550:
#0 0x00007f7e483d3f4c n/a (libc.so.6 + 0x8bf4c)
#1 0x00007f7e48384336 raise (libc.so.6 + 0x3c336)
#2 0x00007f7e4836c8f7 abort (libc.so.6 + 0x248f7)
#3 0x00007f7e4836d96f n/a (libc.so.6 + 0x2596f)
#4 0x00007f7e48449c5b __fortify_fail (libc.so.6 + 0x101c5b)
#5 0x00007f7e4844adc6 __stack_chk_fail (libc.so.6 + 0x102dc6)
#6 0x000056347aa83d7d n/a (spotify + 0xd58d7d)
#7 0x00007f7e4836e470 n/a (libc.so.6 + 0x26470)
#8 0x00007f7e4836e529 __libc_start_main (libc.so.6 + 0x26529)
#9 0x000056347aa8266e _start (spotify + 0xd5766e)

Stack trace of thread 1039551:
#0 0x00007f7e483cebfe n/a (libc.so.6 + 0x86bfe)
#1 0x00007f7e483d177a pthread_cond_timedwait (libc.so.6 + 0x8977a)
#2 0x00007f7e5001acbe n/a (libcef.so + 0x6a1acbe)
#3 0x00007f7e500444fd n/a (libcef.so + 0x6a444fd)
#4 0x00007f7e4ffc1f6c n/a (libcef.so + 0x69c1f6c)
#5 0x00007f7e50001b4d n/a (libcef.so + 0x6a01b4d)
#6 0x00007f7e50001cd4 n/a (libcef.so + 0x6a01cd4)
#7 0x00007f7e5001b3a7 n/a (libcef.so + 0x6a1b3a7)
#8 0x00007f7e483d2270 n/a (libc.so.6 + 0x8a270)
#9 0x00007f7e4843dfec n/a (libc.so.6 + 0xf5fec)

Stack trace of thread 1039554:
#0 0x00007f7e483cebfe n/a (libc.so.6 + 0x86bfe)
#1 0x00007f7e483d1442 pthread_cond_wait (libc.so.6 + 0x89442)
#2 0x00007f7e5001ab96 n/a (libcef.so + 0x6a1ab96)
#3 0x00007f7e500444d3 n/a (libcef.so + 0x6a444d3)
#4 0x00007f7e4ffc1f6c n/a (libcef.so + 0x69c1f6c)
#5 0x00007f7e4fffe16d n/a (libcef.so + 0x69fe16d)
#6 0x00007f7e4fffd9e9 n/a (libcef.so + 0x69fd9e9)
#7 0x00007f7e4fffd68d n/a (libcef.so + 0x69fd68d)
#8 0x00007f7e4fffd59d n/a (libcef.so + 0x69fd59d)
#9 0x00007f7e5001b3a7 n/a (libcef.so + 0x6a1b3a7)
#10 0x00007f7e483d2270 n/a (libc.so.6 + 0x8a270)
#11 0x00007f7e4843dfec n/a (libc.so.6 + 0xf5fec)

Stack trace of thread 1039553:
#0 0x00007f7e483cebfe n/a (libc.so.6 + 0x86bfe)
#1 0x00007f7e483d1442 pthread_cond_wait (libc.so.6 + 0x89442)
#2 0x00007f7e5001ab96 n/a (libcef.so + 0x6a1ab96)
#3 0x00007f7e500444d3 n/a (libcef.so + 0x6a444d3)
#4 0x00007f7e4ffc1f6c n/a (libcef.so + 0x69c1f6c)
#5 0x00007f7e4fffe16d n/a (libcef.so + 0x69fe16d)
#6 0x00007f7e4fffd9e9 n/a (libcef.so + 0x69fd9e9)
#7 0x00007f7e4fffd68d n/a (libcef.so + 0x69fd68d)
#8 0x00007f7e4fffd59d n/a (libcef.so + 0x69fd59d)
#9 0x00007f7e5001b3a7 n/a (libcef.so + 0x6a1b3a7)
#10 0x00007f7e483d2270 n/a (libc.so.6 + 0x8a270)
#11 0x00007f7e4843dfec n/a (libc.so.6 + 0xf5fec)
ELF object binary architecture: AMD x86-64

2024-11-25 08:56:30 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Deactivated successfully.
2024-11-25 08:56:30 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Consumed 444ms CPU time, 134.4M memory peak.
2024-11-25 08:56:30 +01:00; zephyr; user.debug; drkonqi-coredump-processor[1039590]: "/opt/spotify/spotify-client/spotify" 1039550 "/var/lib/systemd/coredump/core.spotify.20001.f45496c8d78c4de9a2655cca19bf4157.1039550.1732521389000000.zst"
2024-11-25 08:56:30 +01:00; zephyr; daemon.info; systemd[3818]: Started Launch DrKonqi for a systemd-coredump crash (PID 1039590/UID 0).
2024-11-25 08:56:30 +01:00; zephyr; user.warning; drkonqi-coredump-launcher[1039596]: Unable to find file for pid 1039550 expected at "kcrash-metadata/spotify.f45496c8d78c4de9a2655cca19bf4157.1039550.ini"
2024-11-25 08:56:30 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Deactivated successfully.
2024-11-25 08:56:30 +01:00; zephyr; user.warning; drkonqi-coredump-launcher[1039596]: Nothing handled the dump 😮

 

Spotify Snap (1.2.48.405.gf2c48e6f) binary crashing:

 

2024-11-25 12:05:02 +01:00; zephyr; daemon.info; systemd-coredump[1068063]: Process 1067952 (spotify) of user 20001 terminated abnormally with signal 6/ABRT, processing...
2024-11-25 12:05:02 +01:00; zephyr; daemon.info; systemd[1]: Started Process Core Dump (PID 1068063/UID 0).
2024-11-25 12:05:02 +01:00; zephyr; daemon.info; systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
2024-11-25 12:05:03 +01:00; zephyr; local0.crit; systemd-coredump[1068064]: Process 1067952 (spotify) of user 20001 dumped core.

Stack trace of thread 1067952:
#0 0x00007f521189f00b n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

2024-11-25 12:05:03 +01:00; zephyr; user.debug; drkonqi-coredump-processor[1068065]: "/snap/spotify/80/usr/share/spotify/spotify" 1067952 "/var/lib/systemd/coredump/core.spotify.20001.f45496c8d78c4de9a2655cca19bf4157.1067952.1732532702000000.zst"
2024-11-25 12:05:03 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Deactivated successfully.
2024-11-25 12:05:03 +01:00; zephyr; daemon.info; systemd[3818]: Started Launch DrKonqi for a systemd-coredump crash (PID 1068065/UID 0).
2024-11-25 12:05:03 +01:00; zephyr; user.warning; drkonqi-coredump-launcher[1068071]: Unable to find file for pid 1067952 expected at "kcrash-metadata/spotify.f45496c8d78c4de9a2655cca19bf4157.1067952.ini"
2024-11-25 12:05:03 +01:00; zephyr; user.warning; drkonqi-coredump-launcher[1068071]: Nothing handled the dump 😮
2024-11-25 12:05:03 +01:00; zephyr; daemon.info; systemd[1]:**bleep**: Deactivated successfully.

 

Kernel info (.config attached):

zephyr ~ # uname -a

Linux zephyr 6.1.119-gentoo-x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 23 11:53:09 CET 2024 x86_64 Intel(R) Core(TM)**bleep** GenuineIntel GNU/Linux
zephyr ~ #

 

If you need any more info, please let me know.

 

Cheers,

Wolfram

Reply
21 Replies

Adding --no-zygote also fixed the crashes for me on Gentoo Linux (tested using 1.2.56.502.ga68d2d4f). Thanks! 🤗

The zygote process in chromium is responsible for setup and bookkeeping of the namespace sandbox. Disabling that is usually not what you want.

Since I don't feel very confident about the Spotify app quality and test coverage when I see long standing stack smashing issues,

I would rather live with a few coredumps than letting Spotify run without  the chromium sandbox.

Suggested posts

Let's introduce ourselves!

Hey there you,   Yeah, you! 😁   Welcome - we're glad you joined the Spotify Community!   While you here, let's have a fun game and get…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random