This bug has been here for a long time and quite known in the community, but I can't find a solution. Whenever I break a block, I get a vert short but very noticable lag spike. I run at roughly 140-180 fps in 1.13 but when I mine anywhere, the average fps drops to 40-60 (it spikes to ~2fps, but it averages out). these spikes last about two or three times as long underwater. This problem doesn't only occur in 1.13.
When you do some research for this bug, you find posts like:
All come down to the same thing: Lower your ram, Java is not great at handeling garbage. I tried this. (Only using the simple arguments; -Xmx and -Xms) I allocated bit by bit more RAM. For -Xmx, I used steps of 128mb and 64m for -Xms. Above -Xmx512m -Xms256m it stopped effecting my game (continueing the spikes) until I hit the 3gb mark, of which I started noticing immense spikes by clearing ram. This gave me the impression that this is not caused by a memory issue.
I am currently allocating to Minecraft using the following arguments: -Xmx2g -Xms718m (the standard options didn't really change anything) in the minecraft launcher itself.
The "Configure Java" -> Java -> View arguments:
*see down below
Other options I have tried:
Lowering the game to the lowest settings possible (and uncapping fps), and although the effect was much less noticable duo the extreme fps, it still spikes.
Smooth Lightning to off.
VBO's on.
VBO's off.
Every MipMap level.
entity shadows off.
Every Particles level.
Giving both instances of JavaW higher priority in task manager.
Closing everything else besides Minecraft.
Reinstalling minecraft
Optimising the game via GForce Experience (latest drivers).
My system specs:
CPU: Intel i5 4670 3.4GHz
GPU: MSI GTX 970 4gb
RAM: 24GB DDR3 ram
Java: Java 8 161 (64-bit) update
Windows: Latest Windows 10 update (64-bit)
My laptop does not have this issue. Specs:
CPU: Intel i7 7700HQ 2.8GHz
GPU: MSI GTX 1050 2gb
RAM: 8GB DDR4 ram
Java: Java 8 161 (64-bit) update
Windows: Latest Windows 10 update (64-bit)
using the standard arguments in the launcher.
I'm out of ideas... Any help would be appriciated.
EDIT :
I have asked the same question on Stack Overflow and we were able to print the output of the Garbage Collector to a .txt file. I don't exactly know what the effects are of Allocation Failures but this seems to be a breakthrough in the issue..
That is NOT how you allocate ram to minecraft, you do it via settings in the launcher, the method you are using will allocate that much to anything using java on the computer
Bumb, and (which I will also include in an edit above): I have aksed the same question on StackOverflow and we were able to print the java Garbage Collector output to the following file: https://drive.google.com/file/d/1-J2ul5NjfWAMQd9h1ytOHO8uxQUXWVdo/view. I don't exactly know what this means but it seems like it is something important to the issue. I am currently researching allocation failures and the effects of it.
Rollback Post to RevisionRollBack
Debugging: investegating a murder where you are the murderer.
To post a comment, please login or register a new account.
This bug has been here for a long time and quite known in the community, but I can't find a solution. Whenever I break a block, I get a vert short but very noticable lag spike. I run at roughly 140-180 fps in 1.13 but when I mine anywhere, the average fps drops to 40-60 (it spikes to ~2fps, but it averages out). these spikes last about two or three times as long underwater. This problem doesn't only occur in 1.13.
When you do some research for this bug, you find posts like:
All come down to the same thing: Lower your ram, Java is not great at handeling garbage. I tried this. (Only using the simple arguments; -Xmx and -Xms) I allocated bit by bit more RAM. For -Xmx, I used steps of 128mb and 64m for -Xms. Above -Xmx512m -Xms256m it stopped effecting my game (continueing the spikes) until I hit the 3gb mark, of which I started noticing immense spikes by clearing ram. This gave me the impression that this is not caused by a memory issue.
I am currently allocating to Minecraft using the following arguments: -Xmx2g -Xms718m (the standard options didn't really change anything) in the minecraft launcher itself.
The "Configure Java" -> Java -> View arguments:
*see down below
Other options I have tried:
My system specs:
CPU: Intel i5 4670 3.4GHz
GPU: MSI GTX 970 4gb
RAM: 24GB DDR3 ram
Java: Java 8 161 (64-bit) update
Windows: Latest Windows 10 update (64-bit)
My laptop does not have this issue. Specs:
CPU: Intel i7 7700HQ 2.8GHz
GPU: MSI GTX 1050 2gb
RAM: 8GB DDR4 ram
Java: Java 8 161 (64-bit) update
Windows: Latest Windows 10 update (64-bit)
using the standard arguments in the launcher.
I'm out of ideas... Any help would be appriciated.
EDIT :
I have asked the same question on Stack Overflow and we were able to print the output of the Garbage Collector to a .txt file. I don't exactly know what the effects are of Allocation Failures but this seems to be a breakthrough in the issue..
Debugging: investegating a murder where you are the murderer.
bump
Debugging: investegating a murder where you are the murderer.
-
View User Profile
-
View Posts
-
Send Message
ModeratorI know. I thought i made that clear. I edited the post.
Debugging: investegating a murder where you are the murderer.
Bumb, and (which I will also include in an edit above): I have aksed the same question on StackOverflow and we were able to print the java Garbage Collector output to the following file: https://drive.google.com/file/d/1-J2ul5NjfWAMQd9h1ytOHO8uxQUXWVdo/view. I don't exactly know what this means but it seems like it is something important to the issue. I am currently researching allocation failures and the effects of it.
Debugging: investegating a murder where you are the murderer.