Bug 1951468

Summary: [abrt] pipewire: pw_array_ensure_size(): pipewire killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: pipewireAssignee: Wim Taymans <wtaymans>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: brunovern.a, information, vquintans, wtaymans
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/dd26145549c3930bfffd672a18a8a52465cd6223
Whiteboard: abrt_hash:fe3225d94bd0909ee63ad6f51b5d883b02bb8185;VARIANT_ID=workstation;
Fixed In Version: pipewire-0.3.26-4.fc34 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-02 02:03:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Mikhail 2021-04-20 08:09:56 UTC
Description of problem:
Try to stream my desktop with OBS

Version-Release number of selected component:
pipewire-0.3.25-1.fc35

Additional info:
reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/pipewire.service
cmdline:        /usr/bin/pipewire
crash_function: pw_array_ensure_size
executable:     /usr/bin/pipewire
journald_cursor: s=ec12f31a1b5c4e0a9cfb8f25879eed63;i=29d4f;b=a829f6e7afff486ba63d5a121ed690e4;m=8a8bb3311;t=5c062f1a7abad;x=13f7c45107fe03ec
kernel:         5.12.0-0.rc8.191.fc35.x86_64+debug
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 1950677

Comment 1 Mikhail 2021-04-20 08:10:00 UTC
Created attachment 1773679 [details]
File: backtrace

Comment 2 Mikhail 2021-04-20 08:10:02 UTC
Created attachment 1773680 [details]
File: core_backtrace

Comment 3 Mikhail 2021-04-20 08:10:03 UTC
Created attachment 1773681 [details]
File: cpuinfo

Comment 4 Mikhail 2021-04-20 08:10:05 UTC
Created attachment 1773682 [details]
File: dso_list

Comment 5 Mikhail 2021-04-20 08:10:06 UTC
Created attachment 1773683 [details]
File: environ

Comment 6 Mikhail 2021-04-20 08:10:07 UTC
Created attachment 1773684 [details]
File: exploitable

Comment 7 Mikhail 2021-04-20 08:10:08 UTC
Created attachment 1773685 [details]
File: limits

Comment 8 Mikhail 2021-04-20 08:10:09 UTC
Created attachment 1773686 [details]
File: maps

Comment 9 Mikhail 2021-04-20 08:10:11 UTC
Created attachment 1773687 [details]
File: mountinfo

Comment 10 Mikhail 2021-04-20 08:10:13 UTC
Created attachment 1773688 [details]
File: open_fds

Comment 11 Mikhail 2021-04-20 08:10:14 UTC
Created attachment 1773689 [details]
File: proc_pid_status

Comment 12 Mikhail 2021-04-20 08:10:16 UTC
Created attachment 1773690 [details]
File: var_log_messages

Comment 13 Fedora Update System 2021-04-29 07:57:03 UTC
FEDORA-2021-03756cf274 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-03756cf274

Comment 14 Fedora Update System 2021-04-29 17:11:02 UTC
FEDORA-2021-03756cf274 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-03756cf274`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-03756cf274

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2021-05-02 02:03:18 UTC
FEDORA-2021-03756cf274 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.