Alright, my problem is simple. Before I go into the problem, I'll tell you my PC specs so that you can see why this is a problem.
i7-3630 QM processor, Dual GT750m's with 2GB DDR5 VRAM each for a total of 4GB, 16GB DDR3 RAM.
I don't know if the resolution for the screen would effect it, but I assume it would. 1920x1080.
My problem is that every time I start the game, it runs fine for a little bit. But after it loads all of the chunks it starts to have massive lag spikes before displaying the out of memory screen. Any solutions? Help is greatly appreciated, thank you.
Game performance that degrades over time and then gets OOM can be caused if your video drivers are leaking memory.
You should see that the memory on the F3 screen does not grow out of control, and yet you still run out of memory.
Probably you are running 32bit Java. You should first try running with 64bit Java. This will have two effects: 1) you'll be using 64bit versions of the drivers which are more likely to be correct 2) you will have a much higher limit before you could possibly "run out of memory".
Game performance that degrades over time and then gets OOM can be caused if your video drivers are leaking memory.
You should see that the memory on the F3 screen does not grow out of control, and yet you still run out of memory.
Probably you are running 32bit Java. You should first try running with 64bit Java. This will have two effects: 1) you'll be using 64bit versions of the drivers which are more likely to be correct 2) you will have a much higher limit before you could possibly "run out of memory".
Considering the GT750m's were released last month, I can conceivably see how the drivers might be faulty. I uninstalled Java and reinstalled the 64 bit version, and it seemed to fix the problem. Thank you for the help, both of you.
How the drivers might be faulty? As a software developer I hate to break it to you that code ships with bugs. Known bugs.
The Java 32bit on 64 bit OS's has been well known for a while here, across multiple driver versions, and probably both AMD and Nvidia.
It could be a couple of different things (at least).
Given that the primary concern would be the 64bit versions:
The 32bit compatible drivers might be not managing their memory tightly enough (32bit processes can't be larger than 2GB, period.)
The 32bit versions could have 32/64 bit mix ups that weren't detected during QA (see: primary concern is the 64bit versions).
The 32bit versions could be completely different code bases with unique bugs that weren't detected during QA. (See: primary concern is the 64bit version)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
i7-3630 QM processor, Dual GT750m's with 2GB DDR5 VRAM each for a total of 4GB, 16GB DDR3 RAM.
I don't know if the resolution for the screen would effect it, but I assume it would. 1920x1080.
My problem is that every time I start the game, it runs fine for a little bit. But after it loads all of the chunks it starts to have massive lag spikes before displaying the out of memory screen. Any solutions? Help is greatly appreciated, thank you.
I've already tried that tutorial, but it didn't work for me. Would the fact that I'm using Windows 8 make a difference?
Then try using this tutorial instead. It has steps for Windows 8 users.
You should see that the memory on the F3 screen does not grow out of control, and yet you still run out of memory.
Probably you are running 32bit Java. You should first try running with 64bit Java. This will have two effects: 1) you'll be using 64bit versions of the drivers which are more likely to be correct 2) you will have a much higher limit before you could possibly "run out of memory".
Considering the GT750m's were released last month, I can conceivably see how the drivers might be faulty. I uninstalled Java and reinstalled the 64 bit version, and it seemed to fix the problem. Thank you for the help, both of you.
The Java 32bit on 64 bit OS's has been well known for a while here, across multiple driver versions, and probably both AMD and Nvidia.
It could be a couple of different things (at least).
Given that the primary concern would be the 64bit versions:
The 32bit compatible drivers might be not managing their memory tightly enough (32bit processes can't be larger than 2GB, period.)
The 32bit versions could have 32/64 bit mix ups that weren't detected during QA (see: primary concern is the 64bit versions).
The 32bit versions could be completely different code bases with unique bugs that weren't detected during QA. (See: primary concern is the 64bit version)