pipewire-media-session crashed with SIGSEGV

[Najib]

How to solution the system crash to my hardware

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: Thu Feb 25 10:54:00 2021
ExecutablePath: /usr/bin/pipewire-media-session
InstallationDate: Installed on 2021-02-18 (6 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcCmdline: /usr/bin/pipewire-media-session
SegvAnalysis:
 Segfault happened at: 0x55d5d32e1a83: mov 0x10(%rdx),%rax
 PC (0x55d5d32e1a83) 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 2021-02-22 (3 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
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 #1916716, 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.