game remains in ram

[1vanK]

Elden_Ring.exe (runned through Port Proton) still exists in memory after exit. Without preload the game closes normally. What can be done about this?

[arunanshub]

Do you mind using https://github.com/arunanshub/preload-rs instead and report back? This is a newer rust based implementation.

[1vanK]

I could try, but I need a miniguide on how to compile and install it xD

[arunanshub]

Every CI run of preload-rs produces a fresh binary. Feel free to download and run it. https://github.com/arunanshub/preload-rs/actions/runs/13868058049#artifacts

Unfortunately I haven't had the time to create a documention or release build process. 😅

[1vanK]

user@pc-000:~/Загрузки$ sudo ./preload-rs
2025-03-15T08:46:00.822021Z  WARN kernel::state::inner: Cannot get exe path for pid=2865. Am I running as root?
2025-03-15T08:46:00.822104Z  WARN kernel::state::inner: Cannot get exe path for pid=789. Am I running as root?
2025-03-15T08:46:00.822115Z  WARN kernel::state::inner: Cannot get exe path for pid=593. Am I running as root?
2025-03-15T08:46:00.822136Z  WARN kernel::state::inner: Cannot get exe path for pid=208. Am I running as root?
2025-03-15T08:46:00.822204Z  WARN kernel::state::inner: Cannot get exe path for pid=7100. Am I running as root?
2025-03-15T08:46:00.822218Z  WARN kernel::state::inner: Cannot get exe path for pid=101. Am I running as root?
2025-03-15T08:46:00.822228Z  WARN kernel::state::inner: Cannot get exe path for pid=28. Am I running as root?
....

[arunanshub]

Don't worry it's harmless. Basically, preload-rs is unable to stat kernel threads. I have yet to implement ignoring kthreads. Other than that, try increasing verbosity. If you see messages like "readahead X maps", then you know it's working. I'll implement a fix when I have the bandwidth.

…

On Sat, 15 Mar, 2025, 14:18 1vanK, ***@***.***> wrote: ***@***.***:~/Загрузки$ sudo ./preload-rs 2025-03-15T08:46:00.822021Z WARN kernel::state::inner: Cannot get exe path for pid=2865. Am I running as root? 2025-03-15T08:46:00.822104Z WARN kernel::state::inner: Cannot get exe path for pid=789. Am I running as root? 2025-03-15T08:46:00.822115Z WARN kernel::state::inner: Cannot get exe path for pid=593. Am I running as root? 2025-03-15T08:46:00.822136Z WARN kernel::state::inner: Cannot get exe path for pid=208. Am I running as root? 2025-03-15T08:46:00.822204Z WARN kernel::state::inner: Cannot get exe path for pid=7100. Am I running as root? 2025-03-15T08:46:00.822218Z WARN kernel::state::inner: Cannot get exe path for pid=101. Am I running as root? 2025-03-15T08:46:00.822228Z WARN kernel::state::inner: Cannot get exe path for pid=28. Am I running as root? — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALRQYQ4NH7OZSMKRX52MLF32UPSMTAVCNFSM6AAAAABZB7QHR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRWGM3DAMBUGU> . You are receiving this because you commented.Message ID: ***@***.***> [image: 1vanK]*1vanK* left a comment (arunanshub/preload#3) <#3 (comment)> ***@***.***:~/Загрузки$ sudo ./preload-rs 2025-03-15T08:46:00.822021Z WARN kernel::state::inner: Cannot get exe path for pid=2865. Am I running as root? 2025-03-15T08:46:00.822104Z WARN kernel::state::inner: Cannot get exe path for pid=789. Am I running as root? 2025-03-15T08:46:00.822115Z WARN kernel::state::inner: Cannot get exe path for pid=593. Am I running as root? 2025-03-15T08:46:00.822136Z WARN kernel::state::inner: Cannot get exe path for pid=208. Am I running as root? 2025-03-15T08:46:00.822204Z WARN kernel::state::inner: Cannot get exe path for pid=7100. Am I running as root? 2025-03-15T08:46:00.822218Z WARN kernel::state::inner: Cannot get exe path for pid=101. Am I running as root? 2025-03-15T08:46:00.822228Z WARN kernel::state::inner: Cannot get exe path for pid=28. Am I running as root? — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALRQYQ4NH7OZSMKRX52MLF32UPSMTAVCNFSM6AAAAABZB7QHR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRWGM3DAMBUGU> . You are receiving this because you commented.Message ID: ***@***.***>

[arunanshub]

Also @1vanK, do you mind reporting your problems over on https://github.com/arunanshub/preload-rs?

Also, make sure to run preload-rs like so:

sudo preload-rs -s state.db

It's important that you let preload-rs collect runtime info and store it somewhere.

[1vanK]

arunanshub/preload-rs#140