[Bug] Red Dead Redemption crashing with Hypervisor disabled #350

New Issue

2024-12-06T14:01:39Z

ghost commented

2024-12-06 14:01:39 +00:00

(Migrated from github.com)

Description of the issue

With Hypervisor disabled, Red Dead Redemption doesn't launch at all, and Ryujinx immediately crashes. Why disabling it? Because with it being enabled, the game starts to freeze after 10-30 minutes.

Reproduction steps

Disable Hypervisor
Try to launch Red Dead Redemption

Log file

Ryujinx_1.2.76_2024-12-06_14-46-31.log

OS

macOS 15.2

Ryujinx version

1.2.76

Game version

No response

CPU

No response

GPU

No response

RAM

No response

List of applied mods

No response

Additional context?

The crash appears to have been caused by an unhandled exception that triggered a termination of the application via a low-level abort signal.

macOS Crash Log analysis

**Crash Origin**

The first entry in the crash trace is:

0 libsystem_kernel.dylib 0x18119f720 __pthread_kill + 8

This indicates that the crash was caused by a SIGABRT signal, typically triggered by calling abort().

**Abort Triggered**

The abort() function was explicitly called, as shown by the following line:

2 libsystem_c.dylib 0x1810e4908 abort + 128

This is often a fallback mechanism when the application encounters a critical error it cannot recover from.

App-Specific Function Calls

The abort was initiated by the application through these methods in the Ryujinx stack:

3 Ryujinx 0x10530fac0 PROCAbort + 68
4 Ryujinx 0x10530f988 PROCEndProcess(void*, unsigned int, int) + 352

These functions likely encapsulate platform-specific code for terminating the application.

Unwinding Managed Exceptions

5 Ryujinx 0x104ee8448 UnwindManagedExceptionPass1(PAL_SEHException&, _CONTEXT*) + 900

This indicates that the application encountered a managed exception (likely in the .NET runtime) that was not caught.

Unhandled Exception

7 Ryujinx 0x104e51b24 IL_Throw(Object*) + 516

The function IL_Throw(Object*) in the stack trace suggests that an exception was thrown in the code but was not handled, causing the termination sequence.

Platform-Specific Signals

11 libsystem_platform.dylib 0x18120ee04 _sigtramp + 56

The _sigtramp function in the trace indicates a signal handler being invoked, possibly as a result of a segmentation fault or another critical error.

Code Execution Leading to the Crash

8 ??? 0x10f44319c ???
9 ??? 0x10f443044 ???
...
27 ??? 0x10ee42400 ???

These indicate regions of memory where the symbol information is missing, likely because they are part of dynamically generated or JIT-compiled code.

### Description of the issue With Hypervisor disabled, Red Dead Redemption doesn't launch at all, and Ryujinx immediately crashes. Why disabling it? Because with it being enabled, the game starts to freeze after 10-30 minutes. ### Reproduction steps 1. Disable Hypervisor 2. Try to launch Red Dead Redemption ### Log file [Ryujinx_1.2.76_2024-12-06_14-46-31.log](https://github.com/user-attachments/files/18038961/Ryujinx_1.2.76_2024-12-06_14-46-31.log) ### OS macOS 15.2 ### Ryujinx version 1.2.76 ### Game version _No response_ ### CPU _No response_ ### GPU _No response_ ### RAM _No response_ ### List of applied mods _No response_ ### Additional context? The crash appears to have been caused by an unhandled exception that triggered a termination of the application via a low-level abort signal. **macOS Crash Log analysis** **Crash Origin** The first entry in the crash trace is: 0 libsystem_kernel.dylib 0x18119f720 __pthread_kill + 8 This indicates that the crash was caused by a SIGABRT signal, typically triggered by calling abort(). **Abort Triggered** The abort() function was explicitly called, as shown by the following line: 2 libsystem_c.dylib 0x1810e4908 abort + 128 This is often a fallback mechanism when the application encounters a critical error it cannot recover from. **App-Specific Function Calls** The abort was initiated by the application through these methods in the Ryujinx stack: 3 Ryujinx 0x10530fac0 PROCAbort + 68 4 Ryujinx 0x10530f988 PROCEndProcess(void*, unsigned int, int) + 352 These functions likely encapsulate platform-specific code for terminating the application. **Unwinding Managed Exceptions** 5 Ryujinx 0x104ee8448 UnwindManagedExceptionPass1(PAL_SEHException&, _CONTEXT*) + 900 This indicates that the application encountered a managed exception (likely in the .NET runtime) that was not caught. **Unhandled Exception** 7 Ryujinx 0x104e51b24 IL_Throw(Object*) + 516 The function IL_Throw(Object*) in the stack trace suggests that an exception was thrown in the code but was not handled, causing the termination sequence. **Platform-Specific Signals** 11 libsystem_platform.dylib 0x18120ee04 _sigtramp + 56 The _sigtramp function in the trace indicates a signal handler being invoked, possibly as a result of a segmentation fault or another critical error. **Code Execution Leading to the Crash** 8 ??? 0x10f44319c ??? 9 ??? 0x10f443044 ??? ... 27 ??? 0x10ee42400 ??? These indicate regions of memory where the symbol information is missing, likely because they are part of dynamically generated or JIT-compiled code.

ghost commented

2024-12-26 09:12:06 +00:00

(Migrated from github.com)

Fixed in 1.2.78. If it still occurs, clear your cache.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MeloNX/Ryujinx-ryubing#350