Jump to content

Severe memory leak in Experiment 52b


Peter Han
  • Branch: Live Branch Version: Windows Fixed

The Experiment 52B (SapTree in-game) allocates a list when looking for food to eat. However, it never throws the list away; particularly when large quantities of food are available for the tree to eat, this omission can leak 1 MB or more per cycle.

Specifically in SapTree.StatesInstance.CheckForFood, the pooled list is never recycled after allocation, so instances will constantly be created and never collected as they are still alive in the ListPool instance.

No log file identifying the actual issue will be produced unless the game actually runs out of memory.


Steps to Reproduce
  • Land on a Spaced Out planetoid containing Experiment 52b
  • Drop large amounts of food and other debris nearby (many different items nearby make the leak much faster)
  • Wait for a few cycles
  • Notice that memory usage is increasing
  • Like 4
  • Big Ups 1



User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...