[MC-11715] Memory Leak when using HD Textures Created: 13/Mar/13  Updated: 23/Mar/13  Resolved: 13/Mar/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.5
Fix Version/s: None

Type: Bug
Reporter: tyteen4a03 Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: memory-leak
Environment:

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1
Language: Chinese (Traditional) (Regional Setting: Chinese (Traditional))
Processor: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (4 CPUs), ~3.1GHz
Memory: 8192MB RAM
Available OS Memory: 8028MB RAM
Page File: 7246MB used, 6786MB available


Issue Links:
Duplicate
duplicates MC-11439 Memory leak switching texture packs Resolved
Confirmation Status: Unconfirmed

 Description   

When using an HD Texture pack with a resolution higher than 64x64, one begins to experience serious FPS drop. When using a texture pack with a resolution higher than 256x256, the game will freeze and/or finally spit out this error:

java.lang.OutOfMemoryError: Direct buffer memory
at java.nio.Bits.reserveMemory(Bits.java:632)
at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:97)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:288)
at bii.a(SourceFile:395)
at bii.<init>(SourceFile:135)
at bii.<init>(SourceFile:107)
at bik.a(SourceFile:127)
at bik.c(SourceFile:100)
at bil.b(SourceFile:80)
at bfy.d(SourceFile:350)
at bfy.c(SourceFile:301)
at bjr.a(SourceFile:146)
at axn.a(SourceFile:175)
at bjq.a(SourceFile:109)
at bfk.b(SourceFile:768)
at net.minecraft.client.Minecraft.K(SourceFile:595)
at net.minecraft.client.Minecraft.run(SourceFile:524)
at java.lang.Thread.run(Thread.java:662)

(Memory at that points hits around 220,000K, approximately 6GB of RAM was being used at that moment)



 Comments   
Comment by Tails [ 13/Mar/13 ]

Duplicate of MC-11439, please use the search function to see if your bug has already been submitted. Currently over 54% of tickets are being closed as duplicate.

Generated at Sun Jan 12 12:28:33 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.