Page MenuHomeFeedback Tracker

Linux: Broken error messages on failure to allocate sufficient memory
New, WishlistPublic


If the Linux Dedicated Server is started with too small a -maxMem= value to load a mission a lot of (unhelpful) error messages are printed, none of which point into the (approximate) direction of -maxMem=. Clients currently connected to the server will simply drop back to the mission vote screen without any error messages being displayed.

Examples of server log error messages:

  • Warning: no type entry inside class ...
  • Warning Message: class 'bin\config.bin/...' is not defined ('...' accessed)
  • Warning Message: '/' is not a value
  • Warning Message: No entry 'bin\config.bin/...'.

I attached the server's stdout for -maxMem=2047 (works) and -maxMem=4095 (doesn't work, see bug #22322) as well as a diff between the two to filter out the garbage. {F25409} {F25410} {F25411}


Legacy ID
Dedicated Server
Steps To Reproduce
  1. start the server with -maxMem=2047
  2. load a mission, be happy (everything works)
  3. restart with -maxMem=4095
  4. load a mission (shouldn't be too simple, zeus modules and a few vehicles should do the trick)
  5. clients drop back to the mission vote screen
  6. server stdout contains lots of unhelpful error messages

Event Timeline

Actium edited Steps To Reproduce. (Show Details)Jan 17 2015, 12:34 AM
Actium edited Additional Information. (Show Details)
Actium set Category to Dedicated Server.
Actium set Reproducibility to Always.
Actium set Severity to None.
Actium set Resolution to Open.
Actium set Legacy ID to 3339540558.May 7 2016, 8:06 PM