[GH-ISSUE #3882] [APP BUG]: shadps4 closing behavior after crash on linux #1162

New issue

Open

opened 2026-02-27 21:10:17 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 21:10:17 +03:00

Owner

Originally created by @Sx1Fl0NdqlkM6N4s2pswXKUI0k9FKTaOckLbNXu on GitHub (Dec 28, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3882

Checklist

I have searched for a similar issue in this repository and did not find one.
I am using an official build obtained from releases or updated one of those builds using its in-app updater.

Describe the Bug

So this is more of a question rather then a proper bug report, as due to severly underperforming hardware, I would assume there could be more layers which may add to the issues (running bloodborne with all performance patches, mods, via bblauncher and mangohud and lossless scaling on top of it).

The Issue:

Like 98% of the time, when game crashes, I could simply go to htop and send 9/SIGKILL to shadps4 and it closes as expected.
But sometimes, after game crashed (still hogging ram), it cannot be killed by any combiantion of user/sudo kill/pkill/killall.

The appimage is obviously running as user.
Also attemted to simply turn off pc via poweroff, but then I got stuck in tty as apparently system also couldn't resolve it on it's own.
- I THINK, I've noticed some "shadps4" mounting point which couldn't be unmounted on it's own?

Reproduction Steps

Expected Behavior

No response

Specify OS Version

debian testing

CPU

Ryzen 5 PRO 2400G

GPU

Ryzen 5 PRO 2400G (Radeon RX Vega 11)

Amount of RAM in GB

24GB

Originally created by @Sx1Fl0NdqlkM6N4s2pswXKUI0k9FKTaOckLbNXu on GitHub (Dec 28, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3882 ### Checklist - [x] I have searched for a similar issue in this repository and did not find one. - [x] I am using an official build obtained from [releases](https://github.com/shadps4-emu/shadPS4/releases) or updated one of those builds using its in-app updater. ### Describe the Bug So this is more of a question rather then a proper bug report, as due to severly underperforming hardware, I would assume there could be more layers which may add to the issues (running bloodborne with all performance patches, mods, via bblauncher and mangohud and lossless scaling on top of it). The Issue: 1. Like 98% of the time, when game crashes, I could simply go to htop and send 9/SIGKILL to shadps4 and it closes as expected. 2. But sometimes, after game crashed (still hogging ram), it **cannot be killed by any combiantion of user/sudo kill/pkill/killall**. - The appimage is obviously running as user. - Also attemted to simply turn off pc via poweroff, but then I got stuck in tty as apparently system also couldn't resolve it on it's own. - I THINK, I've noticed some "shadps4" **mounting point** which couldn't be unmounted on it's own? ### Reproduction Steps - ### Expected Behavior _No response_ ### Specify OS Version debian testing ### CPU Ryzen 5 PRO 2400G ### GPU Ryzen 5 PRO 2400G (Radeon RX Vega 11) ### Amount of RAM in GB 24GB

kerem commented

2026-02-27 21:10:17 +03:00

Author

Owner

@kalaposfos13 commented on GitHub (Dec 28, 2025):

Can the issue be replicated using the official launcher, not using Mangohud and Lossless Scaling, and using only a minimal (preferably none) set of mods/patches?

@kalaposfos13 commented on GitHub (Dec 28, 2025): Can the issue be replicated using the official launcher, not using Mangohud and Lossless Scaling, and using only a minimal (preferably none) set of mods/patches?

kerem commented

2026-02-27 21:10:18 +03:00

Author

Owner

@Sx1Fl0NdqlkM6N4s2pswXKUI0k9FKTaOckLbNXu commented on GitHub (Dec 29, 2025):

Can the issue be replicated using the official launcher, not using Mangohud and Lossless Scaling, and using only a minimal (preferably none) set of mods/patches?

It's why I said it's more of a question, for "what steps does shadps4 takes to close itself from appimage after crash".

But ig, I'll try to read debug docs, trim down some of the less essentiall stuff, and pay more attention throughout, for like 2 free gaming days of time to see if issue persists. 😔

@Sx1Fl0NdqlkM6N4s2pswXKUI0k9FKTaOckLbNXu commented on GitHub (Dec 29, 2025): > Can the issue be replicated using the official launcher, not using Mangohud and Lossless Scaling, and using only a minimal (preferably none) set of mods/patches? It's why I said it's more of a question, for "what steps does shadps4 takes to close itself from appimage after crash". But ig, I'll try to read debug docs, trim down some of the less essentiall stuff, and pay more attention throughout, for like 2 free gaming days of time to see if issue persists. 😔