Hi everyone,
I am looking for some advice regarding an Out-of-Memory (OOM) issue with Mempool on my setup. The strange thing is that this only started happening recently; it used to run without any problems in the past. I really don’t understand where this is suddenly coming from, especially because I have another node with the exact same hardware specifications and software versions, and that one runs perfectly fine without any memory issues at all.
Here are the details of the crashing node:
-
Hardware: Intel NUC, 8 GB RAM, 2TB SSD, i5
-
OS: StartOS v0.3.5.1
-
The Problem: Mempool (version 3.2.1) causes Out-of-Memory (OOM) crashes and completely fills up my RAM within a few hours.
-
What I’ve already discovered: The process refuses to listen to manual SSH commands to limit the RAM. StartOS continuously forces the startup with
node --max-old-space-size=16384baked into the wrapper scripts, which obviously crashes my 8GB system. -
Sideload failed: I already tried to sideload Mempool version 3.3.1 (which supposedly fixes the memory limits for 8GB devices), but the
.s9pkfile gets rejected. I suspect this is because the new package is built with the new SDK for the upcoming StartOS 0.4.0.
Does anyone know a workaround to limit the Mempool memory size on StartOS 0.3.5.1 without the system overwriting it on every restart? Or is there any other temporary fix to keep my node stable with 8GB RAM until 0.4.0 drops?
Thanks in advance for any help!




