Visual Scripting - Runaway Memory Usage
Visual Scripting Tool occasionally enters a loop in which is grabs more and more memory from the OS until all Window memory is allocated. The whole computer becomes extremely sluggish while this is happening. Closing VST releases all the memory and the system returns to normal.
This happens about once every couple of days when I'm working on a scenario. I haven't found any way to trigger it on demand.
The last time this happened I began immediately after I clicked the "Run Scenario" button. The game was not running before I clicked the button. The game didn't finish loading until I closed VST. This was the first time I'd run the game after waking the computer up. VST was started before the computer went to sleep.
This screenshot shows Windows releasing approximately 20 Gb of RAM when I closed VST.
Curiously, if you look at VST in Task Manager then it has high CPU usage but the memory usage appears to be lower than normal. e.g. 100 Mb.
I have the same bug
For the record, I'm using Windows 10 Professional with 32 Gb of RAM, a Ryzen 3700X CPU and a GeForce RTX 2060 GPU. I login with a user account not an admin account.
For the record, I'm using Windows 10 Professional with 32 Gb of RAM, a Ryzen 3700X CPU and a GeForce RTX 2060 GPU. I login with a user account not an admin account.
It's just happened again. I left VST running last night. This morning I woke the PC from sleep, maximised VST and noticed that the script editor windows were not rendering correctly.
I did not attempt to launch the game so I guess the bug has nothing to do with that.
Here are some screen shots of Task Manager during the bug. I have an 8 core CPU so the CPU usage suggests one core was running at very high load. You can see that VRageEditor grabs all available memory.
After a while the memory is still allocated as far as windows is concerned but it doesn't appear to be assigned to VRageEditor in Task Manager.
Clicking the close button in the top right hand corner of the app caused VST to close immediately and release all memory back to Windows.
It's just happened again. I left VST running last night. This morning I woke the PC from sleep, maximised VST and noticed that the script editor windows were not rendering correctly.
I did not attempt to launch the game so I guess the bug has nothing to do with that.
Here are some screen shots of Task Manager during the bug. I have an 8 core CPU so the CPU usage suggests one core was running at very high load. You can see that VRageEditor grabs all available memory.
After a while the memory is still allocated as far as windows is concerned but it doesn't appear to be assigned to VRageEditor in Task Manager.
Clicking the close button in the top right hand corner of the app caused VST to close immediately and release all memory back to Windows.
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
I've definitely seen this bug triggered by using the "Run Scenario" button to launch Space Engineers. It's happened at least 4 times now. That means there are 2 different triggers for the bug; coming out of hibernate and launching the game.
I've definitely seen this bug triggered by using the "Run Scenario" button to launch Space Engineers. It's happened at least 4 times now. That means there are 2 different triggers for the bug; coming out of hibernate and launching the game.
Replies have been locked on this page!