So, a couple weeks ago, I went to go launch Minecraft and jump into a singleplayer world. The problem is: every time I log onto a world, my framerate will instantly tank to about 20 FPS and keep getting worse and worse until the game crashes or sends me to the title screen. I've tried starting a new world, updating my drivers, and minimizing graphics settings but nothing has made any progress. My setup is pretty decent (GTX 970, i5 processor, 8 GB RAM off the top of my head) and I can play much more graphically intensive programs just fine. This leads me to believe this is a issue of memory allowance. When I managed to press F3 before I crashed one time, I noticed I was only getting something like 512 MB of memory usage even when the game was struggling to operate and the line graph for memory usage was spiking well beyond that threshold. Problem is, when I went into the launcher settings and updated the allowed RAM from 1 GB to 4 GB, nothing changed. I was still only using 512-ish MB.
So, my question is two-fold: 1. Is Minecraft not being allowed enough RAM to run properly and causing me trouble and 2. How can I solve this problem so my game stops crashing. I've posted a sample crash log in a pastebin down below for clarification. I noticed the phrase "out of memory" popped up in there once, again pointing to memory being the issue. If you have any further questions feel free to ask. Thank you.
I think you have -Xmx512M in the _JAVA_OPTIONS variable in your environment settings, To remedy this,
Press the Windows key and the Pause/Break key simultaneously
A window should popup, click on "Advanced system settings"
Click on "Environment Variables"
Delete the _JAVA_OPTIONS entry.
Rollback Post to RevisionRollBack
Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
Actually, wait. I relaunched it again and it seems to be working just fine now. I'll post back if I have any problems, but I think I might be good. Thanks!
Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
Hiya,
So, a couple weeks ago, I went to go launch Minecraft and jump into a singleplayer world. The problem is: every time I log onto a world, my framerate will instantly tank to about 20 FPS and keep getting worse and worse until the game crashes or sends me to the title screen. I've tried starting a new world, updating my drivers, and minimizing graphics settings but nothing has made any progress. My setup is pretty decent (GTX 970, i5 processor, 8 GB RAM off the top of my head) and I can play much more graphically intensive programs just fine. This leads me to believe this is a issue of memory allowance. When I managed to press F3 before I crashed one time, I noticed I was only getting something like 512 MB of memory usage even when the game was struggling to operate and the line graph for memory usage was spiking well beyond that threshold. Problem is, when I went into the launcher settings and updated the allowed RAM from 1 GB to 4 GB, nothing changed. I was still only using 512-ish MB.
So, my question is two-fold: 1. Is Minecraft not being allowed enough RAM to run properly and causing me trouble and 2. How can I solve this problem so my game stops crashing. I've posted a sample crash log in a pastebin down below for clarification. I noticed the phrase "out of memory" popped up in there once, again pointing to memory being the issue. If you have any further questions feel free to ask. Thank you.
https://pastebin.com/0tY3PbhT
I think you have -Xmx512M in the _JAVA_OPTIONS variable in your environment settings, To remedy this,
Gave that a try, deleted it, hit okay, relaunched, but it crashed again. Here's the crash log:
https://pastebin.com/GjXQ0dML
Actually, wait. I relaunched it again and it seems to be working just fine now. I'll post back if I have any problems, but I think I might be good. Thanks!
I'm glad that it worked!