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}