cyberbeat

Finally a backtrace: ``` Thread 1 (Thread 0x7fd3f5ffb700 (LWP 24765)): #0 0x00007fd429f57c6b in raise () from /lib64/libc.so.6 #1 0x00007fd429f59305 in abort () from /lib64/libc.so.6 #2 0x00007fd429f4fc6a in __assert_fail_base () from...

I also recognized this, and wait for the next crash (if there is any, after my pipewire update to pipewire 0.3.80)

Here is some more debuginfo: ``` Thread 1 (Thread 0x7f7d8f7fe700 (LWP 6267)): #0 0x00007f7dca306c6b in raise () from /lib64/libc.so.6 #1 0x00007f7dca308305 in abort () from /lib64/libc.so.6 #2 0x00007f7dca2fec6a in __assert_fail_base...

I hope the next time, I can also deliver debuginfo for pipewire-spa calls.

Now with all debug-info-packages (also pipewire libspa-support), using pipewire 0.3.82, libasound 1.2.6.1 ``` Thread 1 (Thread 0x7f5d167fc700 (LWP 15928)): #0 0x00007f5d5033ec6b in raise () from /lib64/libc.so.6 #1 0x00007f5d50340305 in abort...

Yes, I already use 0.3.84, and did not have any crash until now. Many thanks @fbriere !

@fbriere could you have a look also at https://github.com/LubosD/twinkle/issues/323, I know this is hard to debug, but perhaps you have a suggestion, how I can investigate? I also could put...