Hi there Issue:
I am having apparent random issues with system freezes.
I play modded minecraft and the system will suddenly just freeze. The system will no longer respond to any input and the network controller will no longer respond to ping.
I cannot seem to find anything in the logs as it appears that whatever is happening its stopping before it gets a chance to write to file?
I am wondering if its a memory leak issue?
Or maybe the AMD driver?
I am unsure how to diagnose properly without the logs being dumped. Any help on tracking down greatly appreciated!
I highly doubt it is a memory leak. That kind of thing is a very rare occurrence in this day and age. I see that you are using x11. Seems like a lot of problems with it lately. Kde plasma seems to be having input issues as it just starts thrashing if you throw too much at it in a short period of time.
Hmm. I thought I was. The login screen shows Wayland, but I believe I have mistakenly thought this meant Wayland selected, rather than an option.
I have logged in and selected Wayland.
Confirmed using Wayland now:
❯ echo $XDG_SESSION_TYPE
wayland
I assumed memory leak as the behaviour has vastly improved after running some performance and memory leak mods on Minecraft. I was surprised when it happened again after a few days of stability.
I’ll run this for a bit and report back. I understand that its potentially the kernel and note that that is also suggested. I’ll eliminate one thing at a time (and would prefer Wayland regardless). If behaviour continues I’ll try rollling back to LTS kernel and go from there.
Thanks for the suggestion! Another member suggested using Wayland. I will try that first to eliminate as its easy to do and one thing at a time. If the behaviour persists that I will use this as a next step.
It seems to be more stable on Wayland.
However, I am still noting memory dropping over time. I am wondering if its just a minecraft thing - thats why thought memory leak and applied the appropriate performance mods.
I do have another installation of Manjaro and experienced the same thing though when watching Youtube and its been rock solid since changing to Wayland.
At present, I am just monitoring the RAM and when dropping to far I save the game, quit, then go back in.
The thing that lead me to write this post though is that this is relatively new behaviour. I have been putting up with it for a few weeks, maybe a bit more?
Would the next step be to downgrade the kernel? I dont want to waste anyones time if the consensus is that this is not related to the OS itself.
No I don’t think you have, you have only zram which is not the same as a swap on disk. I would consider adding a swapfile it only takes a few minutes. Swapping to disk is important, otherwise you can crash/freeze your system. Swap - ArchWiki
But with a swap you will still get slow downs, the only thing you can do is somehow lower the quality of the game or get more ram.
Well I’m new to btrfs and I didn’t have the patience to figure it out, so I just made a separate regular swap partition during install. You should stay on btrfs, auto snapping is great. You could also reformat another partition.
Or you could try, what the btrfs wiki says… I just went with what I know already, because that article is missing a few commands I think.
Filename Type Size Used Priority
/dev/zram0 partition 14143484 512 100
/dev/nvme0n1p2 partition 14142784 0 -2
OK. So a swap file helped with RAM starvation.
However, the issue just reoccurred. What is different this time is that I can ping the machine and even SSH. This is new.
The question is, what to look for?
Checking the journal I cannot see anything obvious. Any clues?
I can see some clean up of files right before hand and then me logging in remotely but nothing else. I have htop running and it has not stopped. But system is unresponsive to keyboard and mouse and game is hung.