Dedicated server crash nonstop all of a sudden

[Ms.Snor]

We've been playing co-op, two of us, on a dedicated server the past few weeks. It's Open World and we have built up a big main base and smaller shacks here and there. For two (real) days now we've been working on clearing a straight path through the forest, removing trees, shrubs, rocks, and placing wood and stone piles along the way with geode lights to mark the path.

Today we suddenly started have the issue that the server has started crashing nonstop and we can't play anymore. We have joined either both OR one at a time to test it. The last known spot where we were working in the forest seems to be the most crash-prone. It can crash within a minute being there and collecting shrubs or rocks from the ground. But playing away from that area is still crashing, although it offers longer working gameplay, like maybe 10-15 minutes before it crashes.

The way it crashes is that the server is "stopped" and we both locally see:
"Error Code:
Network failure, lost connection to host - 028
Network failure, lost connection to host (P2P session error)"
^even though we are on a dedicated server. The server goes off, disappears, and has to be started again.

We have tried validating our files locally, and reinstalled the game locally, as per an older Developer comment about leftover files causing issues via Steam updates. It doesn't really feel like the issue could be on our own side though, since it happens to us both individually all of a sudden on this server. Waiting on a response from the server provider for help server-side.

A common warning that gets really spammed on the server log file, in case this means anything, is:
LogEnvQueryGeneratorRecentDamageCausers: Warning: Failed to generate, DamagedActorContext wasn't valid

We have played a lot since the latest update without crashes. It just started out of nowhere today while we were maybe an hour into a co-op session today. And since then, just nonstop crashes.

[Ms.Snor]

So this was a memory issue. The server had 8 GB of memory, the game suddenly reached that point, and the server was being cut off for reaching the limit. The server owner had to upgrade to 12 GB memory to run the dedicated server.

It's only been two players playing on there for about three weeks. We've barely even discovered the map. Seems excessive.

[taryngar]

It seems like the server backend has suddenly developed a major base memory increase, as well as a sudden leak that causes it to OOM the server and get killed. I'm running a dedicated server (linux on Wine) and have run into the exact same problem. I've had the same setup for a few months now, running the same open world Prometheus map, but today after this past update even the idle memory usage is over 8GB, and it completely ran the instance out of 12GB. It happened multiple times, too.

I hope the devs are reading this and can look into what might have happened in the past week's update that could cause a memory spike. It makes the game downright unplayable.

[BigRussianBoss ☭ ⓏⓄⓋ]

Как проблему решить? Что значит "пришлось обновлять до 12г" физически или где то в файлах прописывать нужно.