Bug 1948238 - pipewire crashes octave
Summary: pipewire crashes octave
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-11 00:31 UTC by Dmitri A. Sergatskov
Modified: 2022-06-08 01:08 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-08 01:08:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dmitri A. Sergatskov 2021-04-11 00:31:59 UTC
Description of problem:
octave crshes with segfault at exit, if used audio interface

Version-Release number of selected component (if applicable):
pipewire 0.3.25-1
octave 5.2.0 (fedora's rpm) and/or current dev version
How reproducible:

100

Steps to Reproduce:
1. start octave 
2. at octave prompt do "test /usr/share/octave/5.2.0/etc/tests/libinterp/dldfcn/audiodevinfo.cc-tst"
3.exit octave

Actual results:
octave:2> test /usr/share/octave/5.2.0/etc/tests/libinterp/dldfcn/audiodevinfo.cc-tst
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
PASSES 4 out of 4 tests
octave:3> 

fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault (core dumped)


Expected results:
no crash

Additional info:

running (under gdb) the same test with self compiled current dev version of octave compiled with debug symbols and no optimization:

octave:2> exit

Thread 19 "QThread" received signal SIGSEGV, Segmentation fault.
<...deleted...>

Thread 19 (Thread 0x7fff531cd640 (LWP 3372) "QThread"):
#0  0x00007fff4f723cb0 in  ()
#1  0x00007fff4f6470fb in loop_iterate (object=0x62d0067f2428, timeout=<optimized out>) at ../spa/plugins/support/loop.c:308
#2  0x00007fff4f684d13 in do_loop (user_data=0x60400096ab10) at ../src/pipewire/data-loop.c:79
#3  0x00007fffee7d6299 in start_thread () at /lib64/libpthread.so.0
#4  0x00007fffee6fe6a3 in clone () at /lib64/libc.so.6

Also journalctl got flooded with messages like:
Apr 10 20:12:29 dasp53 pipewire[2045]: 93 events suppressed
Apr 10 20:12:29 dasp53 pipewire[2045]: (PortAudio-59) client too slow! rate:1024/48000 pos:16434176 status:triggered

Comment 1 Ben Cotton 2022-05-12 16:44:24 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Ben Cotton 2022-06-08 01:08:51 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.