I haven't played Minecraft in about a year, so it shocked me when I opened the game and every couple of minutes the game wouldn't output a frame for sometimes 30 seconds. I noticed in the debug screen that every time this happens, I'm running on 99% memory. It clears the memory, and in another couple of minutes, it's back to 99%. I have 8 Gb allocated, so not having enough shouldn't be an issue. I'm running on windows 10. I've tried optifine. I've tried updating Java. I haven't tried reinstalling Minecraft, but it had to update, so it's a fresh jar. How can I fix this?
Sounds like Xmn was modified. which it shouldn't have been.
Xmn was being modified. I removed everything from the arguments except for -Xmx4G. It didn't fix the leak, but for some reason, the memory now clears itself much more often, and at smaller amounts, resulting in less lag as a result of the memory leak. I'd still like to be able to prevent the memory from filling up as fast as it is though. I know nothing about Java, by the way, so I may be difficult to work with.
Everything is normal. Memory gets used, it gets abandoned, it gets garbage collected, it's recycled. The circle of life continues.
It's not a leak, it's working.
Now changing Xmn is dangerous. The "new" generation has special rules, it's supposed to be relatively small because it gets garbage collected only when full and then very intensively. Thus your 100% memory used and a stop the world garbage collection.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I haven't played Minecraft in about a year, so it shocked me when I opened the game and every couple of minutes the game wouldn't output a frame for sometimes 30 seconds. I noticed in the debug screen that every time this happens, I'm running on 99% memory. It clears the memory, and in another couple of minutes, it's back to 99%. I have 8 Gb allocated, so not having enough shouldn't be an issue. I'm running on windows 10. I've tried optifine. I've tried updating Java. I haven't tried reinstalling Minecraft, but it had to update, so it's a fresh jar. How can I fix this?
Sounds like Xmn was modified. which it shouldn't have been.
Xmn was being modified. I removed everything from the arguments except for -Xmx4G. It didn't fix the leak, but for some reason, the memory now clears itself much more often, and at smaller amounts, resulting in less lag as a result of the memory leak. I'd still like to be able to prevent the memory from filling up as fast as it is though. I know nothing about Java, by the way, so I may be difficult to work with.
Everything is normal. Memory gets used, it gets abandoned, it gets garbage collected, it's recycled. The circle of life continues.
It's not a leak, it's working.
Now changing Xmn is dangerous. The "new" generation has special rules, it's supposed to be relatively small because it gets garbage collected only when full and then very intensively. Thus your 100% memory used and a stop the world garbage collection.