Minecraft Forums

Though there are no shortage of posts about this game stuttering in forums across the net, I have found no fix that works.

The 'memory' (when viewing with F3 - pic attached) increases to 100% every roughly ten seconds. The game then pauses for an instant, then the memory begins to climb again. It also stutters for an instant in the 30-40% range. So roughly twice every ten seconds my game stops and is unresponsive for a moment, then proceeds normally for a few seconds.

So, newly updated game here (1.8), no mods, default (or with resource pack) no difference. And, not surprisingly (after reading a ton of other forum posts) I run every game I own on at least high, generally ultra, with zero issues. This is explicitly a Minecraft issue, but I've no idea what to do to solve it.

Also worth mentioning, I had little to no issues in 1.7.2 - the last version I played (on this same machine).

Any help would be appreciated! Thx

i7 2.93 GHz (4 core)
8 gigs G Skill
Radeon HD 7970
Win 7 Pro w/64 bit Java

***EDIT*** I also meant to include that this issue happens in exactly the same way even when I am standing still for long periods in game. I find that strange

***EDIT 2 ***
Couple more notes-

I have allocated everything from the default RAM on the game itself and the server, to up to 4 gigs on each - with no difference.

I have also tried no limits to FPS, 60, 30 and 20 - with no difference.

Why didn't you at least post the whole screen? Then we could see what your render distance is.

Also of interest is the exact Java arguments you are using.

I think you have either pushed up your render distance (which can require more memory than the defaults, depending upon where you set it) or modified Xmn (which you shouldn't have done).

Quote from gerbil»

Why didn't you at least post the whole screen? Then we could see what your render distance is.

I didn't include it because I did not foresee you wanting this information, as it isn't relevant in my situation. Now that you've asked; I have tried everything form 2 chunks to maximum with almost identical results. The increase to 100% memory occurs slightly slower when standing still in the 2 chunk scenario, but it still occurs. Yes, smallest possible render distance, standing still in a virtually empty, new, almost entirely flat world - same results.

I changed nothing in the 'java arguments' anywhere other than the specific amount of RAM being allocted. If there is some specific argument I 'should' be using, you might have included that.

So no, I didn't 'push the render distance up' or 'modify the Xmn'. I am only desperately trying to get a severely broken, horribly optimized game, that I also happen to love playing when it works, running smoothly as it did for me (and thousands of others) in past versions. Again, this is the same machine that ran the last version wonderfully. Same machine, same java, same...everything, but the Minecraft update itself. I have changed nothing, merely updated the game, and now it is unplayable...broken.

Simply Google 'stutter 1.8 Minecraft' to see just how many thousands of others have has this exact issue, have participated in polls about it, have had year-long ongoing threads on Reddit about it.... the list goes on. Do not blame the customer friend. With the millions upon millions made off of this game, you'd think they could at least get the base game stable after all of these years. *sigh*

Quote from godlesswonder»

I didn't include it because I did not foresee you wanting this information, as it isn't relevant in my situation. Now that you've asked; I have tried everything form 2 chunks to maximum with almost identical results. The increase to 100% memory occurs slightly slower when standing still in the 2 chunk scenario, but it still occurs. Yes, smallest possible render distance, standing still in a virtually empty, new, almost entirely flat world - same results.

I changed nothing in the 'java arguments' anywhere other than the specific amount of RAM being allocted. If there is some specific argument I 'should' be using, you might have included that.

So no, I didn't 'push the render distance up' or 'modify the Xmn'. I am only desperately trying to get a severely broken, horribly optimized game, that I also happen to love playing when it works, running smoothly as it did for me (and thousands of others) in past versions. Again, this is the same machine that ran the last version wonderfully. Same machine, same java, same...everything, but the Minecraft update itself. I have changed nothing, merely updated the game, and now it is unplayable...broken.

Simply Google 'stutter 1.8 Minecraft' to see just how many thousands of others have has this exact issue, have participated in polls about it, have had year-long ongoing threads on Reddit about it.... the list goes on. Do not blame the customer friend. With the millions upon millions made off of this game, you'd think they could at least get the base game stable after all of these years. *sigh*

I do believe a memory leak fix will happen soon, probably in 1.9, if that's your issue. If it stutters for you the instant you open up the game, I don't know how to help you. If it slowly gets there, and you have to restart the game at some point, that happens to me, as well. Don't actually know how to fix that either. The amount of time it takes for my memory to climb is fairly long, and therefore bearable.

Try other verxions of 1.8, and see if 1.7 has this problem.

Quote from awemanrank100»

I do believe a memory leak fix will happen soon, probably in 1.9, if that's your issue. If it stutters for you the instant you open up the game, I don't know how to help you. If it slowly gets there, and you have to restart the game at some point, that happens to me, as well. Don't actually know how to fix that either. The amount of time it takes for my memory to climb is fairly long, and therefore bearable.

Thanks for the reply. Sadly, it does happen right away. We may never know... (thx again)