[1.191.105] Multiplayer Memory Leak.
Outdated
Since the beginning of this week, SE has had a huge memory leak, especially in Multiplayer.
I can't even load a Keen official server without page filing before the sever can fully load in. My system has 32gb of DDR4 Memory.
Above is a video detailing the problem.
I also attached the game log for the same game session that was recorded in the video.
Files:
SpaceEngineers.log
Log looks like you are running on Extreme Voxel settings. Don't get me wrong, I agree that voxel memory leaks are an issue, but it is debatable whether you can expect an interactive experience from the "screenshot" setting. A repro case based on High might have more weight.
Log looks like you are running on Extreme Voxel settings. Don't get me wrong, I agree that voxel memory leaks are an issue, but it is debatable whether you can expect an interactive experience from the "screenshot" setting. A repro case based on High might have more weight.
Log looks like you are running on Extreme Voxel settings. Don't get me wrong, I agree that voxel memory leaks are an issue, but it is debatable whether you can expect an interactive experience from the "screenshot" setting. A repro case based on High might have more weight.
Log looks like you are running on Extreme Voxel settings. Don't get me wrong, I agree that voxel memory leaks are an issue, but it is debatable whether you can expect an interactive experience from the "screenshot" setting. A repro case based on High might have more weight.
Hello, Engineer!
Thank you for your feedback! Your topic has been added between considered issues.
Please keep voting for the issue as it will help us to identify the most serious bugs.
We really appreciate your patience.
Kind Regards
Keen Software House: QA Department
Hello, Engineer!
Thank you for your feedback! Your topic has been added between considered issues.
Please keep voting for the issue as it will help us to identify the most serious bugs.
We really appreciate your patience.
Kind Regards
Keen Software House: QA Department
Replies have been locked on this page!