pipewire crashed with SIGSEGV

[lotuspsychje]

ubuntu-desktop 24.04 development branch @ 23/11/23 with kernel 6.5.0-10-generic

While browsing around on firefox snap, a pipewire crash occured

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: pipewire-bin 0.3.85-1
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Nov 23 19:34:47 2023
ExecutablePath: /usr/bin/pipewire
InstallationDate: Installed on 2023-11-09 (14 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcCmdline: /usr/bin/pipewire
ProcEnviron:
 LANG=nl_NL.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f2a16bf141e: mov (%r15),%edx
 PC (0x7f2a16bf141e) ok
 source "(%r15)" (0x00000002) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pipewire
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/audioconvert/libspa-audioconvert.so
 ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/audioconvert/libspa-audioconvert.so
 ?? () from /lib/x86_64-linux-gnu/libpipewire-0.3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so
 ?? () from /lib/x86_64-linux-gnu/libpipewire-0.3.so.0
Title: pipewire crashed with SIGSEGV
UpgradeStatus: Upgraded to noble on 2023-11-09 (14 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2027839, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.