Startup Issue with Vintage Story - Vintage Story will run out of memory upon fresh instance

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Callisto’ v2.5.1.8 (Mainline)
Virtualization Docker
Application Vintage Story
Module GenericModule
Running in Container Yes
Current State Stopped

Problem Description

Issue

Fresh instance install of Vintage Story, no matter the settings. Everything is up to date. Never happened on past installs. Happens on two seperate machine installs of AMP.

Unable to complete task
This task could not be completed: Starting Vintage Story… - - State: 3.
Application stopped unexpectedly with exit code 134.

Reproduction Steps

  • Install Vintage Story Instance
  • Setup everything as you have done in the past. There isn’t that much.
  • Boot, or update the server. Runs out of memory in strange ways.

I’m adding to this as I am also running into this issue, both in Amp 2.5 and in Amp 2.6. Interestingly, I was able to modify the server.sh to run the server outside of AMP and that worked without issue.

NB: Occurs regardless of Vintage Story version or mods - this occurs on fresh installs of 1.18, 1.19, and 1.20.
Server is equipped with 64GB of ram and is only utilizing approx 12gb.

Log excerpt from failed operation / run within amp 2.5/2.6:

Loaded Mods: 
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Collections.Generic.List`1.set_Capacity(Int32 value)
   at System.Collections.Generic.List`1.Insert(Int32 index, T item)
   at Newtonsoft.Json.Linq.JContainer.InsertItem(Int32 index, JToken item, Boolean skipParentCheck, Boolean copyAnnotations)
   at Newtonsoft.Json.Linq.JContainer..ctor(JContainer other, JsonCloneSettings settings)
   at Newtonsoft.Json.Linq.JObject.CloneToken(JsonCloneSettings settings)

Log excerpt from proper operation / run outside of amp via server.sh:

27.10.2024 01:55:29 [Notification] Entering runphase RunGame
27.10.2024 01:55:29 [Notification] Starting server threads
27.10.2024 01:55:29 [Event] Dedicated Server now running on Port 42420 and all ips!
27.10.2024 01:55:29 [Event] Return again.
1 Like

It’s an issue with the docker image which Mike hasn’t fixed

You can use greelan/amp:ubuntu as a custom image in the meantime

1 Like

Ach, I had a failure to read - I can open a new topic accordingly as well on that note.
My outofmemory errors occur even when /not/ in Docker mode - and I confirmed with a fresh instance never toggled to Docker as well.

Yeah, that’s a 2.6 issue to do with a .NET setting that AMP has introduced that chokes the memory for child processes.

My docker image gets around it as well xD

1 Like

Gotcha, and good to know! Hopefully that gets patched soon, but glad it’s a known thing - definitely thanks for the referenced image!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.