Crash/Freeze problem as of recent, looking for fix

Ask Fedora
1

Basically, I have never had this happen before until I have recently started playing modded Minecraft with some friends. After some time, and once way sooner while I decided to host the server on the same computer, the whole desktop environment will freeze and come to a halt, and will only move my cursor/update once every minute or so. Not alt+f4’ing or ctl+alt+del will work and I have to restart. Looking at journalctl I see this plastered over and over again, perhaps a memory leak issue? I am not sure which is why I am asking if anyone knows!

Dec 20 09:19:41 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:41 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:41 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:41 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:41 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:41 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:41 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:41 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:42 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:42 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!
Dec 20 09:19:42 fedora kwin_wayland_wrapper[2591]: Key repeat discarded, Wayland compositor doesn’t seem to be processing events fast enough!

2

Could be. What levels of memory usage and CPU usage do you see at the time when this issue happens?

3

It’s near impossible to get those numbers when it’s in that state. Considering just launching the game fresh and joining the server, my ram usage goes to ~19gb/30gb (normal for MC though) it could be that. I am sure my CPU usage wouldn’t be more then 40% however though. I am surprised a memory leak would be able to shut down the whole DE.

4

You could try something like this before you start up the game server:

free -s 5 > ~/memory_log.txt

That will write memory usage every 5 seconds to a text file, and that text file will still be there to review even if you have to reboot the machine.

It depends how the system is configured, for example how aggressive the OOM Killer process is. However I’m no kind of expert on that, others may know more.

5

If free -s 5 > ~/memory_log.txt doesn’t reveal the problem, you can try running journalctl —hostname —follow in a terminal.