[MC-9382] Crash with 512x texture pack Created: 07/Feb/13  Updated: 07/Jun/15  Resolved: 26/Feb/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w06a, Snapshot 13w07a
Fix Version/s: Snapshot 13w09b

Type: Bug
Reporter: iamdarkyoshi Assignee: Unassigned
Resolution: Fixed Votes: 2
Labels: crash

Attachments: Text File crash-2013-02-07_17.18.23-client.txt     Text File crash-2013-02-17_02.53.55-client.txt    
CHK:
Confirmation Status: Community Consensus

 Description   

I used this texture pack: http://www.planetminecraft.com/texture_pack/unibluecraft---a-minecraft-hd-project-512x512/ and i used the "unstitcher" from the Wiki, and tried to apply texture, crashing the client. I cannot enter the game again (it crashes AFTER the Mojang screen unless i change my texture pack in the options.txt file. I have attached my crash report. My client will not enter the game even on my gaming machine. here are my system specs:

OS Name Microsoft Windows 7 Professional
Version 6.1.7600 Build 7600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name LUKE-PC
System Manufacturer ECS
System Model P67H2-A3
System Type x64-based PC
Processor Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz, 3292 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 4.6.5, 5/24/2012
SMBIOS Version 2.7
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume3
Locale United States
Hardware Abstraction Layer Version = "6.1.7600.16385"
User Name Luke-PC\Luke
Time Zone Central Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 16.0 GB
Available Physical Memory 13.3 GB
Total Virtual Memory 31.9 GB
Available Virtual Memory 27.9 GB
Page File Space 16.0 GB
Page File C:\pagefile.sys



 Comments   
Comment by Miguel Aglipay [ 07/Jun/15 ]

I Tried To Open A x512 Texture Pack, And My Minecraft Crashed. How Do I Fix This Issue?

Comment by Matthew Mirvish [ 28/Feb/13 ]

You guys, it isnt ram, its the terrain sticher. Read the crash report

Comment by Anthony Di Gregorio [ 27/Feb/13 ]

Thanks a ton!

Comment by [Mojang] Grum (Erik Broes) [ 26/Feb/13 ]

Limit will be moved to whatever your videocard reports to support.

Comment by Kumasasa [ 25/Feb/13 ]

Ignore the bot.

Comment by Anthony Di Gregorio [ 25/Feb/13 ]

---- Minecraft Crash Report ----
// There are four lights!

Time: 2/7/13 9:21 AM
Description: Rendering screen

java.lang.Error: Couldn't stitch terrain together.
at bht.b(SourceFile:85)
at bfh.c(SourceFile:429)
at bfh.b(SourceFile:357)
at biz.a(SourceFile:148)
at axe.a(SourceFile:175)
at biy.a(SourceFile:111)
at bet.b(SourceFile:764)
at net.minecraft.client.Minecraft.K(SourceFile:597)
at net.minecraft.client.Minecraft.run(SourceFile:526)
at java.lang.Thread.run(Unknown Source)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

– Head –
Stacktrace:
at bht.b(SourceFile:85)
at bfh.c(SourceFile:429)
at bfh.b(SourceFile:357)
at biz.a(SourceFile:148)
at axe.a(SourceFile:175)
at biy.a(SourceFile:111)

– Screen render details –
Details:
Screen name: biy
Mouse location: Scaled: (195, 178). Absolute: (781, 365)
Screen size: Scaled: (480, 270). Absolute: (1920, 1080). Scale factor of 4
Stacktrace:
at bet.b(SourceFile:764)
at net.minecraft.client.Minecraft.K(SourceFile:597)
at net.minecraft.client.Minecraft.run(SourceFile:526)
at java.lang.Thread.run(Unknown Source)

– System Details –
Details:
Minecraft Version: 13w06a
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_09, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 968617824 bytes (923 MB) / 1029046272 bytes (981 MB) up to 1029046272 bytes (981 MB)
JVM Flags: 2 total; -Xmx1024m -Xms1024m
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: No suspicious classes found.
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
LWJGL: 2.4.2
OpenGL: GeForce GT 440/PCIe/SSE2 GL version 4.2.0, NVIDIA Corporation
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Texture Pack: TP 2x512.zip
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~ERROR~ NullPointerException: null

Comment by [Bot] Spam Golem [ 25/Feb/13 ]

I could not find any existing issue that contains any of the crashes mentioned here. However, all of the crash reports that you have provided are from a modded version of Minecraft. Please try to reproduce the crash in a vanilla (non-modded) version of Minecraft and attach that report or this may be dismissed as being caused by a mod.

Comment by iamdarkyoshi [ 17/Feb/13 ]

I'll say. Photoshop wont lag with that size though... I have cs6

Comment by Anthony Di Gregorio [ 17/Feb/13 ]

The amount of RAM you allocate to the game will not matter. The game can NOT stitch together 512x textures. I am assuming this is "as intended". Check your minecraft folder for the "fake terrain" file. (IE: C:\Users\Anthony\AppData\Roaming\.minecraft\stitched_terrain.png)

4096x is the size of that file, and it should be double that for 512 textures. Of course a 8192x PNG gives Photoshop the lags...

Seems, to me, the only fix would be to have Minecraft not use a terrain.png (fake or real...)

Comment by iamdarkyoshi [ 17/Feb/13 ]

i will try mcpatcher, as 128x lags pretty bad on my ATI graphics cards, which each have 2gb of vram.

Comment by Meta [ 17/Feb/13 ]

Tried a 512x512 pack too, got the same crash. (attached crash-2013-02-17_02.53.55-client.txt)

Comment by Anthony Di Gregorio [ 15/Feb/13 ]

Still happening as of Snapshot 13w07a. Reading up on the new texturing format, I am forced to ask: Is this working as intended? Since the game makes a "fake terrain.png" file, and that file seems to be limited in size (4096x or 256x textures)

Like I said before, running the MCPatcher HD textures, I can get up to 2048x before any lag shows up. So it's not a memory issue, well I suppose it is. MCPatcher uses the memory more efficiently than vanilla HD...

Comment by Anthony Di Gregorio [ 10/Feb/13 ]

I can confirm that this is happening, here is a link to my pack made specifically for/with the snapshots. (IE no unstitching) As I finished the textures, the game progressively got laggier, until I completed the IronDoorLower. Once that was done, the game wouldn't even load (Locks up after "Mojang" splash) Got in, same workaround as OPoster here, and when I tried to switch to my pack. Boom! (Same crash report)

I would also like to state, using MCPatcher (before the vanilla HD snapshots) I could get up to 2048x resolution before ANY lag.

Lastly, if one hits escape (single or multiplayer) the lag/FPS drop vanishes. (At least it does for me.)

Pack: https://dl.dropbox.com/u/95865616/TP%202x512.zip

Comment by [Mod] CubeTheThird [ 08/Feb/13 ]

Although your system has lots of ram, your client is only using up to 1GB. I would recommend increasing the maximum if you intend to keep using very large textures.

Comment by iamdarkyoshi [ 08/Feb/13 ]

i doubt it, i have 16GB of ddr3 gaming ram, dual 2gb vram graphics cards, an i5 3.3ghz, and a REALLY crappy hard drive

Comment by Meta [ 08/Feb/13 ]

I guess those 139 MB of texture stuff may be too much for your RAM?

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