Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GIT version] Most recent update of util/atomic.cpp seems to cause segfault while starting any game #9386

Closed
heavysink opened this issue Dec 7, 2020 · 10 comments

Comments

@heavysink
Copy link

heavysink commented Dec 7, 2020

OS:
Archlinux, i7-10750H, RTX2070 Max-Q
rpcs3 git version, cmake option: cmake -DCMAKE_BUILD_TYPE=Debug

Summary:
Most recent update GIT version seems to have segfault when starting any game.

gdb output:

Thread 14 "..pool" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff47fff640 (LWP 123614)]
atomic_wait_engine::wait(void const*, unsigned int, long long __vector(2), unsigned long, long long __vector(2), atomic_wait::info*) (data=0x76fd400 <thread_base::finalize(unsigned long)::s_pool_ctr>, size=8, old_value=...,
timeout=18446744073709551615, mask=..., ext=0x7fff47ffbbd0) at /home/heavysink/src/rpcs3/rpcs3/util/atomic.cpp:1149
1149 atomic_fence_seq_cst();
(gdb) bt
#0 atomic_wait_engine::wait(void const*, unsigned int, long long __vector(2), unsigned long, long long __vector(2), atomic_wait::info*)
(data=0x76fd400 <thread_base::finalize(unsigned long)::s_pool_ctr>, size=8, old_value=..., timeout=18446744073709551615, mask=..., ext=0x7fff47ffbbd0) at /home/heavysink/src/rpcs3/rpcs3/util/atomic.cpp:1149
#1 0x00000000005d8a4c in atomic_wait::list<2u>::wait(atomic_wait_timeout) (this=0x7fff47ffbba0, timeout=atomic_wait_timeout::inf) at /home/heavysink/src/rpcs3/rpcs3/util/atomic.hpp:302
#2 0x00000000005d4023 in thread_base::finalize(unsigned long) (_self=140734401345088) at /home/heavysink/src/rpcs3/Utilities/Thread.cpp:2124
#3 0x0000000008003014 in ()
#4 0x0000000000000000 in ()

RPCS3.log attached
RPCS3.log

@arabek
Copy link
Contributor

arabek commented Dec 7, 2020

Same here.

Doing regression test to see which was the last working commit. Will update here.

Working: 3a0b3a8
Working: 77aa9e5
First Bad: b16cc61 from pull request #9376

@Hirato
Copy link

Hirato commented Dec 7, 2020

can get the segfault by invoking Create Firmware Cache too.
It's a little random, but it will sometimes print things like this to stdout as well.

Segfault writing location 00000000d5d49060 at 00000000006553a7.
Emu Thread Name: 'Progress Dialog Server'.
Thread id = 140556392252992.

RPCS3: Segfault writing location 00000000d5d49060 at 00000000006553a7.
Emu Thread Name: 'Progress Dialog Server'.
Thread id = 140556392252992.

Found exec link: /usr/bin/rpcs3
Debugger: 0

@arabek
Copy link
Contributor

arabek commented Dec 7, 2020

Thread 14 "..pool" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff60a26640 (LWP 171054)]
0x000000000065c0b7 in atomic_wait_engine::wait(void const*, unsigned int, long long __vector(2), unsigned long, long long __vector(2), atomic_wait::info*) ()
(gdb) bt full
#0  0x000000000065c0b7 in atomic_wait_engine::wait(void const*, unsigned int, long long __vector(2), unsigned long, long long __vector(2), atomic_wait::info*)
    ()
No symbol table info available.
#1  0x000000000069793c in thread_base::finalize(unsigned long) ()
No symbol table info available.
#2  0x0000000005003014 in ?? ()
No symbol table info available.
#3  0x0000000000000000 in ?? ()
No symbol table info available.
(gdb) c
Continuing.
Segfault writing location 0000000060a23120 at 000000000065c0b7.
Emu Thread Name: 'Progress Dialog Server'.
Thread id = 140734814643776.

@gamrXerus
Copy link

I can confirm from pr 9376, rpcs3 crashes when trying to boot up a game. I'm on Lubuntu 20.10

@Nekotekina
Copy link
Member

I hope it's fixed now, sorry.

@arabek
Copy link
Contributor

arabek commented Dec 8, 2020

Confirming, fixed by #9388
Thanks!

@MSuih MSuih closed this as completed Dec 8, 2020
@nitroos-ai
Copy link

Still broken for me.
RPCS3.zip

@MSuih
Copy link
Member

MSuih commented Dec 9, 2020

Does it happen if you switch from SPU ASMJIT to LLVM?

And don't load weird libraries as they might cause issues, keep it as "Load Liblv2.sprx only".

@MSuih
Copy link
Member

MSuih commented Dec 9, 2020

#9399 might fix any lingering issues.

@nitroos-ai
Copy link

Yes #9399 fixes my issue. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants