Skip to content

Emulator seg-faults upon resizing active game window (Linux, Xorg, i3wm and NVIDIA) #18131

Closed

Description

@ZephyrCodesStuff

Quick summary

Whenever I launch a game using the Vulkan renderer, and I un-pin the window from the tiling WM, then proceed to resize it, the emulator seg-faults.

Happens every single time I try to resize the game window. Does not happen if I'm resizing the emulator's main Qt GUI window, only for the actively emulated game's window.

Only seems to happen with Vulkan, while it doesn't with OpenGL.

Details

This is the relevant log from the terminal:

zeph@arch ~ [SIGTERM]> rpcs3
Found AppImage path: /home/zeph/Applications/RPCS3.AppImage
[TSC calibration] Available clock sources: 'tsc hpet acpi_pm '
[TSC calibration] Kernel reports the TSC is reliable.
Debugger: 0
Failed to set RLIMIT_MEMLOCK size to 2 GiB. Try to update your system configuration.
RPCS3: Vulkan Device Enumeration Thread: RSX: Found Vulkan-compatible GPU: 'NVIDIA GeForce RTX 4070' running on driver 590.48.1.0
RPCS3: SYS: LLVM version: 19.1.7
RPCS3: SYS: Firmware version: 4.92
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
qt.multimedia.ffmpeg: Using Qt multimedia with FFmpeg version 7.1.1 GPL version 3 or later
RPCS3: RSX: Found Vulkan-compatible GPU: 'NVIDIA GeForce RTX 4070' running on driver 590.48.1.0
RPCS3: RSX [0x0000000]: SYS: 
Segfault reading location 0000000000000018 at 0000557dcbd62c5e.
Emu Thread Name: 'rsx::thread'.

RPCS3: RSX [0x0000000]: SIG: Thread terminated due to fatal error: Segfault reading location 0000000000000018 at 0000557dcbd62c5e.
Emu Thread Name: 'rsx::thread'.

malloc(): unsorted double linked list corrupted

Attach a log file

This is the offending crash log:
RPCS3.log

Attach capture files for visual issues

No response

System configuration

zeph@arch

OS: Arch Linux x86_64
Host: iMacPro1,1 (1.0) /!\ <-- this is spoofed from the OpenCore bootloader
Kernel: Linux 6.18.6-arch1-1
Uptime: 40 mins
Packages: 808 (pacman)
Shell: fish 4.3.3
Display (HPN3442): 1920x1080 in 27", 144 Hz [External]
WM: i3 4.25 (X11)
Cursor: Adwaita
Terminal: kitty 0.45.0
Terminal Font: FiraCodeNF-Reg (11pt)
CPU: Intel(R) Core(TM) i5-14600KF (20) @ 5.30 GHz
GPU 1: NVIDIA GeForce RTX 4070 [Discrete]
GPU 2: AMD Radeon HD 5770
Memory: 6.01 GiB / 31.18 GiB (19%)
Swap: 0 B / 8.00 GiB (0%)
Disk (/): 68.18 GiB / 245.02 GiB (28%) - ext4
Local IP (enp5s0): 192.168.1.34/24
Locale: C.UTF-8

Other details

No response

Activity

  1. Ninetime commented on Feb 1, 2026

    @Ninetime
    Contributor

    The issue doesn't appear to be Linux specific as i can replicate it on Windows 10. Tried with default settings.

    RPCS3.log

  2. digant73 commented on Feb 1, 2026

    @digant73
    Contributor

    please verify if it is a possible regression since 0.0.39-18736 (#18111)

  3. Ninetime commented on Feb 2, 2026

    @Ninetime
    Contributor

    please verify if it is a possible regression since 0.0.39-18736 (#18111)

    For me on Windows, that seems to be the regression point:
    Working - RPCS3-18725.log.gz
    Failing - RPCS3-18736.log
    Failing - RPCS3-18737.log

  4. digant73 commented on Feb 2, 2026

    @digant73
    Contributor

    please verify if it is a possible regression since 0.0.39-18736 (#18111)

    For me on Windows, that seems to be the regression point: Working - RPCS3-18725.log.gz Failing - RPCS3-18736.log Failing - RPCS3-18737.log

    so you are confirming the issue I faced in the same PR. It seems a regression since 0.0.39-18736 (#18111)

  5. self-assigned this
    on Feb 2, 2026
  6. kd-11 commented on Feb 2, 2026

    @kd-11
    Contributor

    @Ninetime How are you resizing exactly? By dragging the border? Or maximize/minimize?

  7. kd-11 commented on Feb 2, 2026

    @kd-11
    Contributor

    #18140 fixes this

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions