The game starts working properly but its RAM consume increase until is too much, literally consuming 12-13 Gb of ram (i have 16) and starts to being so laggy, and it wasnt happening previously. I tried reinstalling the game and it looks stopping at 6gb but after some time it continue increasing its consume again, no matter the world or anythihg. I saw other post about this issue here but it didn't get solved.
[media]Linked issues
duplicates 1
Attachments
Comments 13
migrated
Do you have the "Improve Input Response" option enabled in Video Settings?
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Do you have the "Improve Input Response" option enabled in Video Settings?
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Hi, aye, i have the improve input response enabled, but in previous updates wasn't having this issue
Hi, aye, i have the improve input response enabled, but in previous updates wasn't having this issue
After restarting the game with improve input response disabled is running good, here the RAM consume:
[media]
But why this happens?
After restarting the game with improve input response disabled is running good, here the RAM consume:
[media]
But why this happens?
This issue is being tracked at MCPE-179496, so I am resolving this report as a duplicate.
As to your question, I do not know why the bug occurs, but you can check the comments on the that report for any information.
This issue is being tracked at MCPE-179496, so I am resolving this report as a duplicate.
As to your question, I do not know why the bug occurs, but you can check the comments on the that report for any information.