A couple of weeks back, I noticed my game stuttering and the experience got progressively worse the longer I played.
I opened the Resource Monitor to find the game eating up copious amounts of my RAM.
I noticed it in one world at first, but it seems to affect all the worlds I have played since.
Here is the RAM usage sitting on the start screen, before opening any worlds:
[media]
Now after starting the world and flying around spawn for about 2 to 3 minutes.
[media]
And then, once I've closed the world, the game doesn't really free up that RAM. It holds on to most of it.
[media]Here are my PC specs:
[media][media]I have also linked the .MCWORLD file here so you can take a look at it. I did use a WorldEdit clone add-on previously to do some terrain work. I do not have it activated or included anymore. I did have to turn on "Use Beta API's" to use the add-on, so that's the only experimental feature activated for this world.
I've worked on this world for months, and now I'm worried that all that effort will be for naught. I'm hoping we can find a solution to this problem.
Linked issues
duplicates 1
Attachments
Comments 4
I have repeated this test with the "Improved Input Response" option enabled and disabled, both producing the same result.
I have also repeated this test with a fresh Launcher install, and several uninstall and reinstall cycles of Minecraft, and are up-to-date on my Windows 10 patches and drivers.
The only constant variable is some of my exported .MCWORLD files that I had archived in another directory. I have been importing them back in to do these tests with. I exported them before the first uninstall/reinstall cycle, though the problem has existed since before that.
Update:
I have since confirmed that the "Improved Input Response" setting does indeed cause issues when enabled. I seem to have stable memory performance now with the setting turned off.
It's a shame that the setting is buggy right now.
It did improve the responsiveness of the game when it wasn't eating a hole through my DIMMs
I will close this ticket as a duplicate of MCPE-179496 then.
Do you have the "Improved Input Response" option enabled? (MCPE-179496)