The Meaning of Life, the Universe, and Everything.
Join Date:
7/19/2011
Posts:
42
Member Details
My minecraft started to lag whenever I turn my mouse. I'm not sure why, I looked it up and it seems like it might have something to do with lwjgl? Anyways, I have no idea to fix it. Also, occasionally my minecraft will just crash, and all I'll be doing is walking around. Any help is appreciated!
Also I have updated java, and updated graphics drivers.
EDIT: Seems like allocating more RAM and turning on vsync seemed to help a lot. It isn't totally fixed but much more playable. 1.9 might just need some more optimising.
This is happening because you are using 32 bit Java; how do I know?
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 168374552 bytes (160 MB) / 386187264 bytes (368 MB) up to 1060372480 bytes (1011 MB)
32 bit Java uses the "client VM", whereas 64 bit uses the "server VM" Also, out of memory errors occurring despite plenty of Java heap space remaining (according to this only about 38% of the total was used at any one time) is a classic symptom of 32 bit Java running out of native memory, which is limited to a total of 2 GB. I have my own experience with this; I have 32 bit (including a 32 bit OS) and using a render distance much higher than "Normal" (8 chunks) is asking for an out of memory error - unless I decrease the memory allocated (which sounds contradictory but note that only 368 MB was used at the time of the crash, which occurred because of a lack of native memory. With 1 GB allocated you only have 1 GB of native memory left for the JVM and OpenGL).
This is happening because you are using 32 bit Java; how do I know?
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 168374552 bytes (160 MB) / 386187264 bytes (368 MB) up to 1060372480 bytes (1011 MB)
32 bit Java uses the "client VM", whereas 64 bit uses the "server VM" Also, out of memory errors occurring despite plenty of Java heap space remaining (according to this only about 38% of the total was used at any one time) is a classic symptom of 32 bit Java running out of native memory, which is limited to a total of 2 GB. I have my own experience with this; I have 32 bit (including a 32 bit OS) and using a render distance much higher than "Normal" (8 chunks) is asking for an out of memory error - unless I decrease the memory allocated (which sounds contradictory but note that only 368 MB was used at the time of the crash, which occurred because of a lack of native memory. With 1 GB allocated you only have 1 GB of native memory left for the JVM and OpenGL).
Oops, didn't notice that Minecraft isn't using the 64bit version; however, I still get massive lag when moving my mouse even after changing it. I'll go from 100+ fps down to less than 20.
Rollback Post to RevisionRollBack
Hey
To post a comment, please login or register a new account.
My minecraft started to lag whenever I turn my mouse. I'm not sure why, I looked it up and it seems like it might have something to do with lwjgl? Anyways, I have no idea to fix it. Also, occasionally my minecraft will just crash, and all I'll be doing is walking around. Any help is appreciated!
Also I have updated java, and updated graphics drivers.
==========
Specs
==========
CPU: Amd FX4100
GPU: GTX 560ti
RAM: 8G DDR3
Java: Version 1.8.0_73 64bit
Here's the crash report:
http://pastebin.com/145JCpqw
EDIT: Seems like allocating more RAM and turning on vsync seemed to help a lot. It isn't totally fixed but much more playable. 1.9 might just need some more optimising.
Hey
i think something is up with open gl
Possibly, but is there a fix? Open GL is up to date...
Hey
This is happening because you are using 32 bit Java; how do I know?
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 168374552 bytes (160 MB) / 386187264 bytes (368 MB) up to 1060372480 bytes (1011 MB)
32 bit Java uses the "client VM", whereas 64 bit uses the "server VM" Also, out of memory errors occurring despite plenty of Java heap space remaining (according to this only about 38% of the total was used at any one time) is a classic symptom of 32 bit Java running out of native memory, which is limited to a total of 2 GB. I have my own experience with this; I have 32 bit (including a 32 bit OS) and using a render distance much higher than "Normal" (8 chunks) is asking for an out of memory error - unless I decrease the memory allocated (which sounds contradictory but note that only 368 MB was used at the time of the crash, which occurred because of a lack of native memory. With 1 GB allocated you only have 1 GB of native memory left for the JVM and OpenGL).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Oops, didn't notice that Minecraft isn't using the 64bit version; however, I still get massive lag when moving my mouse even after changing it. I'll go from 100+ fps down to less than 20.
Hey