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

crash when i try to open config UI [macos] #14997

Closed
nsklaus opened this issue Jan 2, 2024 · 17 comments
Closed

crash when i try to open config UI [macos] #14997

nsklaus opened this issue Jan 2, 2024 · 17 comments

Comments

@nsklaus
Copy link

nsklaus commented Jan 2, 2024

Quick summary

immediate crash upon opening config ui.
running on macos 14.3 beta.
this problem started to happen with all recent builds since a little while now, maybe a month or such.

Details

when i click "config" button on rpcs3 toolbar, or if i try to do the same (open config UI) from system menu bar, i get immediate popup indicating a crash and rpcs3 exit.

the popup shows this:

Segfault reading location 000000000000000c at 000000000cf03861.
Thread: Main Thread.
Title: "" (emulation is stopped)
Build: "0.0.29-15900-d6dde225 Alpha | HEAD"
Date: "2024-01-02T11:30:16"
Title: "" (emulation is stopped)
Build: "0.0.29-15900-d6dde225 Alpha | HEAD"
Date: "2024-01-02T11:30:16"

to note:
if i don't try to open the config UI, and i just double click a game in the list, i still get a crash mesage but i can click 'continue/ignore' and the game actualy starts and is playable. i also tried to delete rpcs3 config directory in ~/Library/Application Support/rpcs3/ and start fresh, but the result was the same. no matter what i try, i cannot access config UI anymore.

Attach a log file

RPCS3.log

Attach capture files for visual issues

Screenshot 2024-01-02 at 11 47 29

System configuration

macos 14.3 beta

Other details

apparently last known build to allow opening config UI, was build 0.0.29-15773 back from november 29-2023 (thanks duke on discord for that info).

@agnosticlines
Copy link

agnosticlines commented Jan 8, 2024

Also experienced this, seems to happen 100% of the time when launched as an .app, but when you cd to the directory and run ./rpcs3 you can launch the config UI fine, it's just when you stop emulation it crashes.

Process 83229 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x30)
    frame #0: 0x000000000cf7458f QtWidgets`QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool) const + 127
QtWidgets`QWidgetPrivate::childAtRecursiveHelper:
->  0xcf7458f <+127>: testb  $0x1, 0x30(%r15)
    0xcf74594 <+132>: je     0xcf74560                 ; <+80>
    0xcf74596 <+134>: movq   0x20(%r14), %rdi
    0xcf7459a <+138>: testb  $0x1, 0xc(%rdi)
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x30)
  * frame #0: 0x000000000cf7458f QtWidgets`QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool) const + 127
    frame #1: 0x000000000cf74642 QtWidgets`QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool) const + 306
    frame #2: 0x000000000cf74642 QtWidgets`QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool) const + 306
    frame #3: 0x000000000cf744d4 QtWidgets`QWidgetPrivate::childAt_helper(QPoint const&, bool) const + 116
    frame #4: 0x000000000cf88e11 QtWidgets`___lldb_unnamed_symbol11715 + 273
    frame #5: 0x000000000cf88642 QtWidgets`___lldb_unnamed_symbol11714 + 226
    frame #6: 0x000000000cf22c87 QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 247
    frame #7: 0x000000000cf23a92 QtWidgets`QApplication::notify(QObject*, QEvent*) + 498
    frame #8: 0x000000000de0fe0a QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 170
    frame #9: 0x000000001f424a19 QtGui`QGuiApplicationPrivate::processEnterEvent(QWindowSystemInterfacePrivate::EnterEvent*) + 249
    frame #10: 0x000000001f4800bc QtGui`QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 444
    frame #11: 0x000000002a3f8adf libqcocoa.dylib`___lldb_unnamed_symbol1707 + 415
    frame #12: 0x00007ff814bcf716 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    frame #13: 0x00007ff814bcf6b9 CoreFoundation`__CFRunLoopDoSource0 + 157
    frame #14: 0x00007ff814bcf488 CoreFoundation`__CFRunLoopDoSources0 + 215
    frame #15: 0x00007ff814bce0f8 CoreFoundation`__CFRunLoopRun + 919
    frame #16: 0x00007ff814bcd799 CoreFoundation`CFRunLoopRunSpecific + 557
    frame #17: 0x00007ff81faa29d9 HIToolbox`RunCurrentEventLoopInMode + 292
    frame #18: 0x00007ff81faa2616 HIToolbox`ReceiveNextEventCommon + 201
    frame #19: 0x00007ff81faa2531 HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 66
    frame #20: 0x00007ff81813dd69 AppKit`_DPSNextEvent + 880
    frame #21: 0x00007ff818a47834 AppKit`-[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304
    frame #22: 0x00007ff81812f2e2 AppKit`-[NSApplication run] + 603
    frame #23: 0x000000002a3f685d libqcocoa.dylib`___lldb_unnamed_symbol1686 + 2797
    frame #24: 0x000000000de198f6 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 486
    frame #25: 0x000000000de103f7 QtCore`QCoreApplication::exec() + 119
    frame #26: 0x000000000002ff17 rpcs3`main + 30903
    frame #27: 0x0000000105ac3386 dyld`start + 1942

Also looking at the selector

(lldb) po (SEL)0x00007ff83490f771
"isEqual:"

Seems like a null pointer bug, there's a null check at the start of the settings_dialog::SnapSlider and in the lambda connection function, so I'm not too sure what the root cause is, I also can't build the latest release on Mac because Foundation 13 has issues with old style casts, which I don't feel like trawling through make files and build systems to try omit that argument.

@PrideChung
Copy link

I also can't build the latest release on Mac because Foundation 13 has issues with old style casts, which I don't feel like trawling through make files and build systems to try omit that argument.

there's a PR to fix build errors on mac already: #14452

@PrideChung
Copy link

I also can't build the latest release on Mac because Foundation 13 has issues with old style casts, which I don't feel like trawling through make files and build systems to try omit that argument.

there's a PR to fix build errors on mac already: #14452

Yet another PR addressing the same problem: #15008. Looks promising, will give it a try.

@agnosticlines
Copy link

I also can't build the latest release on Mac because Foundation 13 has issues with old style casts, which I don't feel like trawling through make files and build systems to try omit that argument.

there's a PR to fix build errors on mac already: #14452

Yet another PR addressing the same problem: #15008. Looks promising, will give it a try.

If you can get a debug build with symbols going that'd be awesome, I'll look into this when I have time otherwise but hopefully someone more knowledgable in the code will fix it, I'm kinda just flying blind in a debugger atm

@shinra-electric
Copy link
Contributor

shinra-electric commented Jan 8, 2024

For what it's worth, I can't replicate this issue on Sonoma 14.3 Beta (I'm on Beta 2 now, but I never had the issue on Beta 1 either). I have no issue with the config menu on the release builds or my own local builds. Although I can't currently get a working build of RPCS3 using Sonoma, I have to use Ventura.

I'm on an M1 Pro, From the OP's log it looks like they are on an Apple Silicon Mac too. What processor? Ah, it says M2 Pro in the logs. Does anyone else with this issue have an M2 or M3?

To build with debug symbols you can set the CMake setting -DCMAKE_BUILD_TYPE=Debug or -DCMAKE_BUILD_TYPE=RelWithDebInfo

@agnosticlines
Copy link

agnosticlines commented Jan 8, 2024

For what it's worth, I can't replicate this issue on Sonoma 14.3 Beta (I'm on Beta 2 now, but I never had the issue on Beta 1 either). I have no issue with the config menu on the release builds or my own local builds. Although I can't currently get a working build of RPCS3 using Sonoma, I have to use Ventura.

I'm on an M1 Pro, From the OP's log it looks like they are on an Apple Silicon Mac too. What processor? Ah, it says M2 Pro in the logs. Does anyone else with this issue have an M2 or M3?

To build with debug symbols you can set the CMake setting -DCMAKE_BUILD_TYPE=Debug or -DCMAKE_BUILD_TYPE=RelWithDebInfo

I'm on an M1 Pro too, and yep my comment wasn't saying it wasn't possible or anything, just that I didn't want to fight with build systems like cmake to try build it, thanks though! :) there's issues with the foundation sdk, there's an open PR to fix them though.

Interesting that you don't have this issue though, for some reason it also only repros on one game for me, Little Big Planet 3, the rest it works fine

Based on my very limited debugging (without symbols) seems to crash on an :isEqual selector call

@shinra-electric
Copy link
Contributor

there's issues with the foundation sdk, there's an open PR to fix them though.

Interesting, do you have a link to that?

@nsklaus
Copy link
Author

nsklaus commented Jan 9, 2024

@agnosticlines
reading what you've said, i've just tried to get latest build and start it directly through command line:

cd Downloads/rpcs3-v0.0.30-15924-7504503d_macos/RPCS3.app/Contents/MacOS/
MacOS % ./rpcs3 
[mvk-info] MoltenVK version 1.2.6, supporting Vulkan version 1.2.268.
	The following 102 Vulkan extensions are supported:
....
[mvk-info] GPU device:
		model: Apple M2 Pro
....
[mvk-info] Created VkInstance for Vulkan version 1.0.0, as requested by app, with the following 0 Vulkan extensions enabled:
[mvk-info] Destroyed VkPhysicalDevice for GPU Apple M2 Pro with 0 MB of GPU memory still allocated.
[mvk-info] Destroying VkInstance for Vulkan version 1.0.0 with 0 Vulkan extensions enabled.
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
RPCS3: SYS: 
Segfault reading location 000000000000000c at 000000000cf20861.
Thread: Main Thread.

RPCS3: SIG: Thread terminated due to fatal error: Segfault reading location 000000000000000c at 000000000cf20861.
Thread: Main Thread.

RPCS3: Segfault reading location 000000000000000c at 000000000cf20861.
Thread: Main Thread.

Title: "" (emulation is stopped)
Build: "0.0.30-15924-7504503d Alpha | HEAD"
Date: "2024-01-09T10:32:31"
Debugger: 0
zsh: abort      ./rpcs3

so for me, it's the same as when i start it as an app, meaning, immediate crash upon trying to open anything related to config UI. for info i'm also on 14.3 beta2 (23D5043d), my system is a macbook pro 14" m2pro 16gb of ram (from 2023).

@agnosticlines
Copy link

agnosticlines commented Jan 9, 2024

@agnosticlines reading what you've said, i've just tried to get latest build and start it directly through command line:

Hey, had a look again, went to record a video, you're right, it happens for me sometimes when I open it with ./rpcs3 too, it definitely seems to happen more when I open it as an app, not sure if that's a coincidence, I'm starting to think it's a timing issue or race, given that it seems to be pretty random when it decides to crash, but if I click config the second I can, it crashes 90-95% of the time, that lambda is seeming quite suspect:

void settings_dialog::SnapSlider(QSlider *slider, int interval)
{
	if (!slider)
	{
		return;
	}

	// Snap the slider to the next best interval position if the slider is currently modified with the mouse.
	connect(slider, &QSlider::valueChanged, [this, slider, interval](int value)
	{
		if (!slider || slider != m_current_slider)
		{
			return;
		}
		slider->setValue(utils::rounded_div(value, interval) * interval);
	});

	// Register the slider for the event filter which updates m_current_slider if a QSlider was pressed or released with the mouse.
	// We can't just use sliderPressed and sliderReleased signals to update m_current_slider because those only trigger if the handle was clicked.
	slider->installEventFilter(this);
	m_snap_sliders.insert(slider);
}

Particularly the connect call, but there's a check if it's null in there, I guess the pointer is never truly null, it's always offset by some bytes, so it could be getting corrupted, possibly in a race between it and the objc_msgSend ?

While testing for this issue I've uncovered another dozen or so crashes in UI code, seem to also be race-y issues:

Process 17974 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=2, address=0xc30982d18)
    frame #0: 0x000000000de0fdee QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 142
QtCore`QCoreApplication::notifyInternal2:
->  0xde0fdee <+142>: addl   $0x1, 0x8(%r15)
    0xde0fdf3 <+147>: testb  %bl, %bl
    0xde0fdf5 <+149>: je     0xde0fe0c                 ; <+172>
    0xde0fdf7 <+151>: movq   0x4aeda2(%rip), %rdi      ; QCoreApplication::self
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=2, address=0xc30982d18)
  * frame #0: 0x000000000de0fdee QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 142
    frame #1: 0x000000000de10faa QtCore`QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 1482
    frame #2: 0x000000002a2a1b2b libqcocoa.dylib`___lldb_unnamed_symbol1693 + 315
    frame #3: 0x000000002a2a2adf libqcocoa.dylib`___lldb_unnamed_symbol1707 + 415
    frame #4: 0x00007ff80c053716 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    frame #5: 0x00007ff80c0536b9 CoreFoundation`__CFRunLoopDoSource0 + 157
    frame #6: 0x00007ff80c053488 CoreFoundation`__CFRunLoopDoSources0 + 215
    frame #7: 0x00007ff80c0520f8 CoreFoundation`__CFRunLoopRun + 919
    frame #8: 0x00007ff80c051799 CoreFoundation`CFRunLoopRunSpecific + 557
    frame #9: 0x00007ff816f269d9 HIToolbox`RunCurrentEventLoopInMode + 292
    frame #10: 0x00007ff816f26616 HIToolbox`ReceiveNextEventCommon + 201
    frame #11: 0x00007ff816f26531 HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 66
    frame #12: 0x00007ff80f5c1d69 AppKit`_DPSNextEvent + 880
    frame #13: 0x00007ff80fecb834 AppKit`-[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304
    frame #14: 0x00007ff80f5b32e2 AppKit`-[NSApplication run] + 603
    frame #15: 0x000000002a2a085d libqcocoa.dylib`___lldb_unnamed_symbol1686 + 2797
    frame #16: 0x000000000de198f6 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 486
    frame #17: 0x000000000de103f7 QtCore`QCoreApplication::exec() + 119
    frame #18: 0x000000000002ff17 rpcs3`main + 30903
    frame #19: 0x0000000105ac3386 dyld`start + 1942
Process 17675 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x7265746661003a85)
    frame #0: 0x000000000cf61733 QtWidgets`QWidget::window() const + 19
QtWidgets`QWidget::window:
->  0xcf61733 <+19>: movq   0x20(%rdi), %rcx
    0xcf61737 <+23>: testb  $0x1, 0xc(%rcx)
    0xcf6173b <+27>: jne    0xcf6174a                 ; <+42>
    0xcf6173d <+29>: movq   0x8(%rax), %rcx
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x7265746661003a85)
  * frame #0: 0x000000000cf61733 QtWidgets`QWidget::window() const + 19
    frame #1: 0x000000000cfbf0c8 QtWidgets`QStyleOption::initFrom(QWidget const*) + 24
    frame #2: 0x000000000d093a0b QtWidgets`QGroupBox::initStyleOption(QStyleOptionGroupBox*) const + 43
    frame #3: 0x000000000d0944c8 QtWidgets`QGroupBox::event(QEvent*) + 136
    frame #4: 0x000000000cf22c87 QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 247
    frame #5: 0x000000000cf23a92 QtWidgets`QApplication::notify(QObject*, QEvent*) + 498
    frame #6: 0x000000000de0fe0a QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 170
    frame #7: 0x000000000de10faa QtCore`QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 1482
    frame #8: 0x000000002a2a1b2b libqcocoa.dylib`___lldb_unnamed_symbol1693 + 315
    frame #9: 0x000000002a2a2adf libqcocoa.dylib`___lldb_unnamed_symbol1707 + 415
    frame #10: 0x00007ff80c053716 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    frame #11: 0x00007ff80c0536b9 CoreFoundation`__CFRunLoopDoSource0 + 157
    frame #12: 0x00007ff80c053488 CoreFoundation`__CFRunLoopDoSources0 + 215
    frame #13: 0x00007ff80c0520f8 CoreFoundation`__CFRunLoopRun + 919
    frame #14: 0x00007ff80c051799 CoreFoundation`CFRunLoopRunSpecific + 557
    frame #15: 0x00007ff816f269d9 HIToolbox`RunCurrentEventLoopInMode + 292
    frame #16: 0x00007ff816f26616 HIToolbox`ReceiveNextEventCommon + 201
    frame #17: 0x00007ff816f26531 HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 66
    frame #18: 0x00007ff80f5c1d69 AppKit`_DPSNextEvent + 880
    frame #19: 0x00007ff80fecb834 AppKit`-[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304
    frame #20: 0x00007ff80f5b32e2 AppKit`-[NSApplication run] + 603
    frame #21: 0x000000002a2a085d libqcocoa.dylib`___lldb_unnamed_symbol1686 + 2797
    frame #22: 0x000000000de198f6 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 486
    frame #23: 0x000000000de103f7 QtCore`QCoreApplication::exec() + 119
    frame #24: 0x000000000002ff17 rpcs3`main + 30903
    frame #25: 0x0000000105ac3386 dyld`start + 1942
Process 18735 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x9bc1a0000000128)
    frame #0: 0x000000001f4207da QtGui`QGuiApplicationPrivate::sendQWindowEventToQPlatformWindow(QWindow*, QEvent*) + 42
QtGui`QGuiApplicationPrivate::sendQWindowEventToQPlatformWindow:
->  0x1f4207da <+42>: movq   0x128(%rcx), %rcx
    0x1f4207e1 <+49>: movq   %rax, %rdi
    0x1f4207e4 <+52>: movq   %rbx, %rsi
    0x1f4207e7 <+55>: addq   $0x8, %rsp
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x9bc1a0000000128)
  * frame #0: 0x000000001f4207da QtGui`QGuiApplicationPrivate::sendQWindowEventToQPlatformWindow(QWindow*, QEvent*) + 42
    frame #1: 0x000000000cf238f5 QtWidgets`QApplication::notify(QObject*, QEvent*) + 85
    frame #2: 0x000000000de0fe0a QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 170
    frame #3: 0x000000000de10faa QtCore`QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 1482
    frame #4: 0x000000002a413b2b libqcocoa.dylib`___lldb_unnamed_symbol1693 + 315
    frame #5: 0x000000002a414adf libqcocoa.dylib`___lldb_unnamed_symbol1707 + 415
    frame #6: 0x00007ff80c053716 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    frame #7: 0x00007ff80c0536b9 CoreFoundation`__CFRunLoopDoSource0 + 157
    frame #8: 0x00007ff80c053488 CoreFoundation`__CFRunLoopDoSources0 + 215
    frame #9: 0x00007ff80c0520f8 CoreFoundation`__CFRunLoopRun + 919
    frame #10: 0x00007ff80c051799 CoreFoundation`CFRunLoopRunSpecific + 557
    frame #11: 0x00007ff816f269d9 HIToolbox`RunCurrentEventLoopInMode + 292
    frame #12: 0x00007ff816f26616 HIToolbox`ReceiveNextEventCommon + 201
    frame #13: 0x00007ff816f26531 HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 66
    frame #14: 0x00007ff80f5c1d69 AppKit`_DPSNextEvent + 880
    frame #15: 0x00007ff80fecb834 AppKit`-[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304
    frame #16: 0x00007ff80f5b32e2 AppKit`-[NSApplication run] + 603
    frame #17: 0x000000002a41285d libqcocoa.dylib`___lldb_unnamed_symbol1686 + 2797
    frame #18: 0x000000000de198f6 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 486
    frame #19: 0x000000000de103f7 QtCore`QCoreApplication::exec() + 119
    frame #20: 0x000000000002ff17 rpcs3`main + 30903
    frame #21: 0x0000000105ac3386 dyld`start + 1942

I very much doubt the fault is with the RPCS3 code here given all these bugs, I wonder if the RPCS3 code has just revealed some bad Qt code on macOS.

@agnosticlines
Copy link

there's issues with the foundation sdk, there's an open PR to fix them though.

Interesting, do you have a link to that?

Same ones mentioned earlier in the thread: #14452 and #15008

@shinra-electric
Copy link
Contributor

there's issues with the foundation sdk, there's an open PR to fix them though.

Interesting, do you have a link to that?

Same ones mentioned earlier in the thread: #14452 and #15008

Ah sorry. I thought you meant a PR to fix the issues in the foundation sdk.

@D-elias
Copy link

D-elias commented Jan 26, 2024

On OSX 14.3, M2 Macbook Pro, the only build that works is Rcps3 0.0.28-15308. I click on config and pads on this version, then opened Rcps3 0.0.30-15914 and booted the game, changed the resolution in the older version and it works. After removing all of the Rcps3 system files with a clean install, the current builds only boot the game but clicking on config or pads crashes it. Then when I changed the settings in 0.0.28-15308 and the current build stopped booting games. So I booted in 0.0.30-15914 and it boots in 0.0.28-15308 now.

@meh7an
Copy link

meh7an commented Jan 28, 2024

On OSX 14.3, M2 Macbook Pro, the only build that works is Rcps3 0.0.28-15308.

I have the issue on M3 Max MacOS 14.3, and the last build that boots games and opens config UI is 0.0.29-15696. From what I understood, just after booting the game, it freezes the UI on latest 16011. The freeze is alongside the game window not opening at all. By tapping on enter button, the modal of "Do you really want to boot another game?" appears, unfreezing the UI and showing the logs after the freeze, but just after tapping on no, it will freeze again. Tapping on yes just crashes the app by a Segfault reading location on main thread.

There were some various ways of app's behavior in the updates forward though, there was a build about 159xx that after tapping on No, the game window would open and work, but I'm not sure if it was about my settings or not.

Anyways, I just named 15696 as "RPCS3 LTS" on my apps until a functional build is there.

@meh7an
Copy link

meh7an commented Jan 28, 2024

Something else that I have realized from the config UI crash is that opening one of the options from Configuration menu (like GUI or Audio) has a possibility of opening the UI (let's say 10% times). Directly tapping on Config button on the app never opens it for me.

@meh7an
Copy link

meh7an commented Feb 3, 2024

I have the issue on M3 Max MacOS 14.3, and the last build that boots games and opens config UI is 0.0.29-15696.

Except the Config UI crash problem, everything else was related to SDL plugin and #14999, meaning that disabling SDL gamepad plugin temporarily fixes them all. The effect of the bug just became worse possibly after QT update to 6.6.1, causing the games to not even get opened. Before that, the bug only was causing the emulator to crash just after closing a game.

So basically the workaround for it is to open the game with SDL disabled, and then enabling it while the game is open (which is almost impossible by current config UI crash, because gamepad settings is basically a config page).
Although this action won't affect the config UI.

@KevDoy
Copy link

KevDoy commented Feb 10, 2024

Can confirm this is also happening to me

@mavethee
Copy link

Same here, this was fixed with updating RPCS3 to new Qt version

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

9 participants