Symptoms:
- A dedicated server fails to start on an intermittent basis.
- The server process terminates unexpectedly during initialization.
- Logs show a segmentation fault (signo:11) after the server prefab begins to load.
- CPU usage spikes to high levels during the failed startup attempts.
Cause: The crash could be caused by a significant CPU spike during the server's initialization phase. The Addressables.LoadAssetAsync method triggers this spike. Some hosting platforms may detect this high resource usage as misbehavior. The platform then terminates the server process with a SIGSEGV signal. An Addressables build configuration that is not optimized for the server target platform is the underlying cause of the high CPU usage.
Resolution: To resolve this issue, apply the following changes to the project.
- Lower the server's frame rate during the initialization and asset loading phase.
- Modify the build pipeline. Ensure that Addressables content is always rebuilt specifically for the server target platform (for example, StandaloneLinux64/Server).
More Information: Mismatched debug symbols and executables can produce unreliable stack traces. This makes troubleshooting segmentation faults more difficult. Always perform a clean build to ensure symbols and executables match.
Related Docs: