May 2May 2 Woke up to this error this am "Your server has run out of memory, and processes (potentially required) are being killed off" Log attached. tower-diagnostics-20260502-0929.zip
May 3May 3 Community Expert 20 hours ago, volsherdeers said:Woke up to this error this am "Your server has run out of memory, and processes (potentially required) are being killed off" Log attached.tower-diagnostics-20260502-0929.zipLooks like on May 01 at 0915 and 0916 kate decided to use an absolute crap ton of RAM, so if you were doing something at that time then that's the issue. You can reboot to clear the log so FCP stops warning you, and if it happens again you can investigate further
May 3May 3 Author 4 hours ago, Michael_P said:Looks like on May 01 at 0915 and 0916 kate decided to use an absolute crap ton of RAM, so if you were doing something at that time then that's the issue. You can reboot to clear the log so FCP stops warning you, and if it happens again you can investigate furtherI did notice around the same time while watching a show remotely on Plex then trying to skip forward a few consecutive times, the show would freeze and lockup. Had to completely back out, then resume to continue watching. Same thing happened again shortly thereafter. Using /dev/shm for transcode and /dev/dri for GPU
May 4May 4 Community Expert 17 hours ago, volsherdeers said:I did notice around the same time while watching a show remotely on Plex then trying to skip forward a few consecutive times, the show would freeze and lockup. Had to completely back out, then resume to continue watching. Same thing happened again shortly thereafter. Using /dev/shm for transcode and /dev/dri for GPUKate's a text editor so probably not related to watching plex - if it happens again you can run ps -auxf from the command line to see what process is kicking it off (krusader was running at the time, may have been in there)
May 4May 4 Author 3 hours ago, Michael_P said:Kate's a text editor so probably not related to watching plex - if it happens again you can run ps -auxf from the command line to see what process is kicking it off (krusader was running at the time, may have been in there)Good deal! Thanks...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.