RPCS3 Crash on Fedora 36 start up
Started by jsmtux




2 posts in this topic
jsmtux
Member


0
2 posts 1 threads Joined: Apr 2022
04-24-2022, 10:08 AM -
#1
Hi all,

After a fresh install of Fedora 36, when starting up the appImage for RPCS3, latest version, I get a Segfault pop up. I am pasting here the log and gdb output, since they are quite small. It happens both on an X11 and a Wayland session. It looks like an issue with pipewire...

Code:
RPCS3 v0.0.21-13488-fb27ed4d Alpha | master
12th Gen Intel(R) Core(TM) i5-12600KF | 16 Threads | 15.48 GiB RAM | TSC: 3.686GHz | AVX+ | FMA3
Operating system: POSIX, Name: Linux, Release: 5.17.3-302.fc36.x86_64, Version: #1 SMP PREEMPT Sun Apr 17 13:22:18 UTC 2022
Qt version: Compiled against Qt 5.15.2 | Run-time uses Qt 5.15.2
Current Time: 2022-04-24T12:01:39
Thread time: 0.000000s (0.000000Gc); Faults: 0 [rsx:0, spu:0]; [soft:2 hard:0]; Switches:[vol:0 unvol:0]; Wait:[0.000s, spur:0]
·! 0:00:00.009375 SYS: Initialization times before main(): 0.041497s
·! 0:00:00.009378 SYS: argc: 1, argv: 'rpcs3'
·! 0:00:00.009383 SYS: Maximum open file descriptors: 4096
·F 0:00:00.107736 {TID: 140315826574912} SIG: Thread terminated due to fatal error: Segfault reading location 0000000000000000 at 00007f9e905cfe84.
Thread id = 140315826574912.
Code:
[New Thread 0x7fff417fb640 (LWP 12169)]
[New Thread 0x7fff40ffa640 (LWP 12172)]

Thread 11 "pw-alsoft" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff40ffa640 (LWP 12172)]
client_node_transport (object=0x6f75270, readfd=34, writefd=33, mem_id=0, offset=0, size=2312) at ../pipewire-jack/src/pipewire-jack.c:1538
Downloading source file /usr/src/debug/pipewire-0.3.50-1.fc36.x86_64/redhat-linux-build/../pipewire-jack/src/pipewire-jack.c...
1538        c->socket_source = pw_loop_add_io(c->loop->loop,
(gdb) bt
#0  client_node_transport (object=0x6f75270, readfd=34, writefd=33, mem_id=0,
    offset=0, size=2312) at ../pipewire-jack/src/pipewire-jack.c:1538
#1  0x00007ffff4d8f6fc in client_node_demarshal_transport (
    object=<optimized out>, msg=<optimized out>)
    at ../src/modules/module-client-node/protocol-native.c:400
#2  0x00007ffff4dc897a in process_remote (impl=impl@entry=0x6f9ca60)
    at ../src/modules/module-protocol-native.c:851
#3  0x00007ffff4dc8fd8 in on_remote_data (data=0x6f9ca60, fd=31, mask=1)
    at ../src/modules/module-protocol-native.c:885
#4  0x00007ffff56883f6 in loop_iterate (object=<optimized out>,
    timeout=<optimized out>) at ../spa/plugins/support/loop.c:409
#5  0x00007ffff572f2e2 in do_loop (user_data=0x6f75900)
    at ../src/pipewire/thread-loop.c:262
#6  0x00007ffff2e5b017 in start_thread (arg=<optimized out>)
    at pthread_create.c:442
#7  0x00007ffff2ee06d0 in clone3 ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb) quit

Thanks for your help!
Ani
Administrator
*******


16
4,276 posts 105 threads Joined: Aug 2017
04-24-2022, 01:40 PM -
#2
Can't reproduce on Manjaro Linux 21.2.6
Maybe you can start by trying 0.0.21-13478 on https://rpcs3.net/builds
This post was last modified: 04-24-2022, 01:41 PM by Ani.
    Desktop: Ryzen 7 5800X,   Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
     Laptop: Ryzen 9 5900HX,  Radeon RX 6700M,   2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350,     Radeon R9 280X,    2x4G DDR3 1600MHz, Manjaro Linux
jsmtux
Member


0
2 posts 1 threads Joined: Apr 2022
04-24-2022, 04:15 PM -
#3
Hi Ani,

Just tried with same verison. Same problem, sadly. I've also deleted the .cache and .config folders, no change.


Forum Jump:


Users browsing this thread: 1 Guest(s)