Memory leak when mining with ship mining drills
Solved
Steps to reproduce:
1. Load the attached save,
2. Get in the mining ship and mine the nearest asteroid.
3. Observe memory usage climbs steadily and never goes down even after exiting to the main menu.
Expected:
Memory usage stays roughly the same while mining.
Files:
Bert base - 1.zip
I have the same bug
Can confirm this, it's also being dicussed on reddit where Marek said it's gonna be fixed.
I just don't get why it takes that long to come to stable. This is quite a gamebreaking bug with large miners.
Can confirm this, it's also being dicussed on reddit where Marek said it's gonna be fixed.
I just don't get why it takes that long to come to stable. This is quite a gamebreaking bug with large miners.
Same here, I have also seen other people posting pictures of their memory usage hitting 30 GB. This is a rather major problem that is only solvable by continuously rebooting the game. I wonder how this bug wasn't detected during internal testing, since it is quite obvious.
Same here, I have also seen other people posting pictures of their memory usage hitting 30 GB. This is a rather major problem that is only solvable by continuously rebooting the game. I wonder how this bug wasn't detected during internal testing, since it is quite obvious.
Even in 1.187.101 this hasn't been fixed! According to reddit it's been over a month now that Marek said it's gonna be fixed. This is a damn gamebreaking bug which is super easy to reproduce and can't be that hard to get rid of! Such kind of bugs should be fixed after one day or shouldn't even happen at all. Do you even test your builds once before publishing them? And ignoring posts like these on your new fancy support board doesn't help either.
Even in 1.187.101 this hasn't been fixed! According to reddit it's been over a month now that Marek said it's gonna be fixed. This is a damn gamebreaking bug which is super easy to reproduce and can't be that hard to get rid of! Such kind of bugs should be fixed after one day or shouldn't even happen at all. Do you even test your builds once before publishing them? And ignoring posts like these on your new fancy support board doesn't help either.
Ver. 1.187.2 - Have this problem as well in my SP world. Never had an issue with this before in my 1100+ hrs of game time. Happens in both Experimental and Vanilla. Been playing with no mods in both as well.
Steps to reproduce-
Same as OP, it climbs faster if you do it with "Right Click Mining" usually in increments of about ~10MB (Hand drill) - ~100MB+ (small ship with 3 drills).
Things tried or noticed:
-Changing display settings and gfx settings.
-Cleaning entire system ie. Verifying file integrity, Fresh install, Defrag HDD and Registry, Checking for errors on both Memory and HDD, Virus scans, Rebooting.. Just about everything I could think of on my end that I typically do weekly or monthly. (Waiting for a chance to have my brother test it on his computer to see if he has same problems. Will edit once I have more info on that)
-Restarting the game is the only way to dump the memory and fix the problem. After reloading the save, the RAM is back to normal before doing the mining, and stays consistent until I start mining again.
Expected:
Memory should stay consistent and not steadily climb, or either dump the current usage when a certain limit is hit when modifying/mining the voxels.
Ver. 1.187.2 - Have this problem as well in my SP world. Never had an issue with this before in my 1100+ hrs of game time. Happens in both Experimental and Vanilla. Been playing with no mods in both as well.
Steps to reproduce-
Same as OP, it climbs faster if you do it with "Right Click Mining" usually in increments of about ~10MB (Hand drill) - ~100MB+ (small ship with 3 drills).
Things tried or noticed:
-Changing display settings and gfx settings.
-Cleaning entire system ie. Verifying file integrity, Fresh install, Defrag HDD and Registry, Checking for errors on both Memory and HDD, Virus scans, Rebooting.. Just about everything I could think of on my end that I typically do weekly or monthly. (Waiting for a chance to have my brother test it on his computer to see if he has same problems. Will edit once I have more info on that)
-Restarting the game is the only way to dump the memory and fix the problem. After reloading the save, the RAM is back to normal before doing the mining, and stays consistent until I start mining again.
Expected:
Memory should stay consistent and not steadily climb, or either dump the current usage when a certain limit is hit when modifying/mining the voxels.
I can't stress enough, how big of a problem this one gets!
I'm administrating the space-engineers.de community server, that now runs since the MP update 24/7 without a wipe (so 80 days straight). Through consequent policies on economy and limits we managed to keep it stable with more than 2 million PCU built on close to 500 grids, 1600+ known roids and 20 players online in parallel each and every evening, reaching at least 0.8 simSpeed, often more - but:
Though we restart the server every 4 hours (bash script), the memory does explode - after 2h it grows to a freakin 20GB.
Sideeffects: starting at 12GB, collisions stop to work correctly, resulting in players glitching through walls and planets. Also, connectors won't connect anymore. This is a killer for every public server.
If you'd like, i'll send you the saved file (200MB+) in private, i won't share it in public as i can't give away players positions (PvP intel - you know).
Thx in advance
I can't stress enough, how big of a problem this one gets!
I'm administrating the space-engineers.de community server, that now runs since the MP update 24/7 without a wipe (so 80 days straight). Through consequent policies on economy and limits we managed to keep it stable with more than 2 million PCU built on close to 500 grids, 1600+ known roids and 20 players online in parallel each and every evening, reaching at least 0.8 simSpeed, often more - but:
Though we restart the server every 4 hours (bash script), the memory does explode - after 2h it grows to a freakin 20GB.
Sideeffects: starting at 12GB, collisions stop to work correctly, resulting in players glitching through walls and planets. Also, connectors won't connect anymore. This is a killer for every public server.
If you'd like, i'll send you the saved file (200MB+) in private, i won't share it in public as i can't give away players positions (PvP intel - you know).
Thx in advance
There is another report dealing with the same issue:https://support.keenswh.com/spaceengineers/general/topic/1-187-205-memory-leak-with-mining
There is another report dealing with the same issue:https://support.keenswh.com/spaceengineers/general/topic/1-187-205-memory-leak-with-mining
Got the same issue - unplayable if I start deforming any voxels.
Got the same issue - unplayable if I start deforming any voxels.
I had this issue with this drillrig here. https://steamcommunity.com/sharedfiles/filedetails/?id=1570877168 I removed the small grid parts and was operating it remotely when my game crashed. Tunneling into a cliff causes sim speed to drop to 0.9 on a private singleplayer world and .06 on a dedicated server. Dedicated Server did not crash and sim speed resolves if drillrig is removed. Attached a screenshot of error and task manager during crash.
I had this issue with this drillrig here. https://steamcommunity.com/sharedfiles/filedetails/?id=1570877168 I removed the small grid parts and was operating it remotely when my game crashed. Tunneling into a cliff causes sim speed to drop to 0.9 on a private singleplayer world and .06 on a dedicated server. Dedicated Server did not crash and sim speed resolves if drillrig is removed. Attached a screenshot of error and task manager during crash.
Bump, bump.... unplayable issue for survival mode.
Bump, bump.... unplayable issue for survival mode.
Replies have been locked on this page!