pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes()

[Антон Дерлюк]

https://errors.ubuntu.com/problem/e118c16c7af628a69e39bc59672e7a25ecdc8e6e

---

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: pipewire-bin 0.3.22-1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Feb 24 13:34:26 2021
ExecutablePath: /usr/bin/pipewire-media-session
InstallationDate: Installed on 2018-03-12 (1079 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
ProcCmdline: /usr/bin/pipewire-media-session
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x563fdf54ea83: mov 0x10(%rdx),%rax
 PC (0x563fdf54ea83) ok
 source "0x10(%rdx)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pipewire
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
 ?? () from /usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
 ?? () from /usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
Title: pipewire-media-session crashed with SIGSEGV
UpgradeStatus: Upgraded to hirsute on 2020-11-22 (94 days ago)
UserGroups: N/A
separator:

[Apport retracing service (apport)]

StacktraceTop:
 refresh_auto_default_nodes (impl=0x563fe12a2120) at ../src/examples/media-session/policy-node.c:824
 core_done (data=0x7ffc02899350, id=0, seq=1073741904) at ../src/examples/media-session/media-session.c:1906
 core_event_demarshal_done (object=<optimized out>, msg=<optimized out>) at ../src/modules/module-protocol-native/protocol-native.c:290
 process_remote (impl=impl@entry=0x563fe1283cb0) at ../src/modules/module-protocol-native.c:766
 on_remote_data (data=0x563fe1283cb0, fd=<optimized out>, mask=1) at ../src/modules/module-protocol-native.c:800

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Tracking in https://errors.ubuntu.com/problem/e118c16c7af628a69e39bc59672e7a25ecdc8e6e

[Daniel van Vugt (vanvugt)]

My hirsute system is failing to record/end screencasts with Shift+Ctrl+Alt+R. I think this crash might be the cause.

[Daniel van Vugt (vanvugt)]

Upstream says:

> It's the metadata bug fixed here: 3673265a
> You can uncomment 'metadata' in the modules in
> /etc/pipewire/media-session.d/media-session.conf
> to work around this or apply the patch.

[Daniel van Vugt (vanvugt)]

Workaround:

--- media-session.conf 2021-02-25 17:44:11.451385390 +0800
+++ /etc/pipewire/media-session.d/media-session.conf 2021-02-25 17:44:23.743336178 +0800
@@ -71,7 +71,7 @@
         #libcamera # libcamera udev detection
         suspend-node # suspend inactive nodes
         policy-node # configure and link nodes
- #metadata # export metadata API
+ metadata # export metadata API
         #default-nodes # restore default nodes
         #default-profile # restore default profiles
         #default-routes # restore default route

[Jason (clrn097913)]

Applied available updates and the updates appear to fix this bug..

[Daniel van Vugt (vanvugt)]

There are no updates that fix this bug yet. Please don't change the status unless you know what you're doing.

[Daniel van Vugt (vanvugt)]

Fix proposed to Debian: https://salsa.debian.org/utopia-team/pipewire/-/merge_requests/5

[Launchpad Janitor (janitor)]

This bug was fixed in the package pipewire - 0.3.22-2

---------------
pipewire (0.3.22-2) experimental; urgency=medium

  [ Daniel van Vugt ]
  * Fix "the metadata crash" (LP: #1916716). Using upstream commit
    3673265ae20d7b59e89cad6c5238c232796731b2 which is scheduled for inclusion
    in release 0.3.23.

 -- Iain Lane <email address hidden> Thu, 04 Mar 2021 11:09:52 +0000

[Togo28 (togo28)]

Even after update the bug appears again here today

[Daniel van Vugt (vanvugt)]

Hmm yes, there are still reports of the crash in 0.3.22-2. But 0.3.22-2 has fixed screen recording and remote desktop :)

[Daniel van Vugt (vanvugt)]

Also, this crash has stopped happening for me in 0.3.22-2. So that version is still multiply beneficial to keep.

I've reopened https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/809 to track this crash again.

[Daniel van Vugt (vanvugt)]

I can't find any evidence to support comment #15. It looks like it's fixed. Perhaps the error tracker got confused by someone's unofficial build called "0.3.22-2".

The error tracker shows no more crashes in 0.3.22-2 since it was released, only in 0.3.22-1.