Texture pack memory error

[AusQB]

I've been using Unleashed with Sphax PureBDcraft 128x and several patches for some of the mods available on the Sphax site. I'm also using Optifine and everything works fine.

However, I wanted to add the Sphax Tinker's Construct pack into the base texture pack. I disabled Optifine to avoid the texture limit and it worked fine for a while, but I reverted to the earlier TP with Optifine.

Now when I put Tinker's Construct back in (again with Optifine disabled), the Java process jumps up to 4 GB (allocated 2 out of 8 total) and I get the following lines at the end of the log (before it is just general info and warnings):

Spoiler

2014-02-18 19:07:46 [INFO] [STDERR] Exception in thread "Minecraft main thread" java.lang.OutOfMemoryError: Direct buffer memory
2014-02-18 19:07:46 [INFO] [STDERR] at java.nio.Bits.reserveMemory(Unknown Source)
2014-02-18 19:07:46 [INFO] [STDERR] at java.nio.DirectByteBuffer.<init>(Unknown Source)
2014-02-18 19:07:46 [INFO] [STDERR] at java.nio.ByteBuffer.allocateDirect(Unknown Source)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.renderer.texture.Texture.func_94278_a(Texture.java:313)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.renderer.texture.Texture.<init>(Texture.java:140)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.renderer.texture.Texture.<init>(Texture.java:100)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.renderer.texture.TextureManager.func_94261_a(TextureManager.java:160)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.renderer.texture.TextureManager.createNewTexture(TextureManager.java:118)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.renderer.texture.TextureMap.func_94247_b(TextureMap.java:112)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.renderer.RenderEngine.func_94152_c(RenderEngine.java:522)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.renderer.RenderEngine.func_78352_b(RenderEngine.java:433)
2014-02-18 19:07:46 [INFO] [STDERR] at cpw.mods.fml.client.FMLClientHandler.onInitializationComplete(FMLClientHandler.java:258)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:479)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.MinecraftAppletImpl.func_71384_a(SourceFile:56)
2014-02-18 19:07:46 [INFO] [STDERR] at net.minecraft.client.Minecraft.run(Minecraft.java:733)
2014-02-18 19:07:46 [INFO] [STDERR] at java.lang.Thread.run(Unknown Source)

When I try to use the actual Sphax texture pack compiled specifically for FTB Unleashed (http://bdcraft.net/patch-details?i=46-Feed the Beast Unleashed), Minecraft itself crashes.

I just don't understand why it was working before.

Is there perhaps some lightweight version of Sphax for Tinker's Construct?

 

[rhn]

I have no idea what the error says(no tech whiz). But 2GB allocated might not be enough for a 128x texture pack. Have you tried upping it to 3-4GB?

 

[Wagon153]

Aye, you are running out of memory. Up it to 3-4 gigs, like rhn said.

 

[AusQB]

I have no idea what the error says(no tech whiz). But 2GB allocated might not be enough for a 128x texture pack. Have you tried upping it to 3-4GB?

I have, to no avail. I even set it to 6 and it just went all the way to near 100% usage before I decided to just terminate the process. It was almost like it was loading infinitely.

I had been able to run it perfectly fine before on 2GB (128x + Tinker's patch).

 

[Wagon153]

Maybe you need more permgen? I highly doubt it but it's worth a shot.

 

[rhn]

I have, to no avail. I even set it to 6 and it just went all the way to near 100% usage before I decided to just terminate the process. It was almost like it was loading infinitely.

I had been able to run it perfectly fine before on 2GB (128x + Tinker's patch).

6GB is way too much. With Java using up more RAM than you allocate you would completely choke your system(It would try and use 12GB approx, which probably results in heavy pagefile usage). Try again with 3GB.

 

[kylemcqueen75]

This is simple, you are doing to much than your system can handle. Plain and Simple, if it worked before, something has changed in an update and it is now requiring more than what your pc can give. Just use a smaller texture pack. If you want, paste a full forge log and we can see if anything else is contributing to you running out of memory.