Crash "Tesselating block model" (java.lang.IndexOutOfBoundsException @ java.util.ArrayList.rangeCheck)

Nevermind.

I think it's been fixed with the 'b' snapshot.

It has not been fixed in the 'b' snapshot, I get exactly the same exception in 14w30b. It reports my client as being modded (it isn't) so refuses to accept the crash report.

Also get a false report of being modded and the same crash report

---- Minecraft Crash Report ----
// Uh... Did I do that?

Time: 7/23/14 12:15 PM
Description: Tesselating block model

java.lang.IndexOutOfBoundsException: Index: 1, Size: 0
	at java.util.ArrayList.rangeCheck(Unknown Source)
	at java.util.ArrayList.get(Unknown Source)
	at csu.b(SourceFile:88)
	at chc.a(SourceFile:156)
	at cjs.a(SourceFile:254)
	at cjs.b(SourceFile:111)
	at cjs.a(SourceFile:45)
	at cjs.a(SourceFile:35)
	at cjq.a(SourceFile:62)
	at cmt.b(SourceFile:156)
	at cmm.a(SourceFile:71)
	at cmm.run(SourceFile:31)
	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 java.util.ArrayList.rangeCheck(Unknown Source)
	at java.util.ArrayList.get(Unknown Source)
	at csu.b(SourceFile:88)
	at chc.a(SourceFile:156)
	at cjs.a(SourceFile:254)
	at cjs.b(SourceFile:111)

-- Block model being tesselated --
Details:
	Block: minecraft:tallgrass[type=tall_grass]
	Block location: World: (184,64,250), Chunk: (at 8,4,10 in 11,15; contains blocks 176,0,240 to 191,255,255), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
	Using AO: false
Stacktrace:
	at cjs.a(SourceFile:45)
	at cjs.a(SourceFile:35)

-- Block being tesselated --
Details:
	Block type: ID #31 (tile.tallgrass // azz)
	Block data value: 1 / 0x1 / 0b0001
	Block location: World: (184,64,250), Chunk: (at 8,4,10 in 11,15; contains blocks 176,0,240 to 191,255,255), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Stacktrace:
	at cjq.a(SourceFile:62)
	at cmt.b(SourceFile:156)
	at cmm.a(SourceFile:71)
	at cmm.run(SourceFile:31)
	at java.lang.Thread.run(Unknown Source)

-- System Details --
Details:
	Minecraft Version: 14w30b
	Operating System: Windows 7 (amd64) version 6.1
	Java Version: 1.7.0_60, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 174446840 bytes (166 MB) / 499646464 bytes (476 MB) up to 1908932608 bytes (1820 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2G
	IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95

I'm having this same crash about "Tesselating block model". Here is the crash-report. Hope it helps.

I too am getting a false "it looks like your client is modded, so we can't accept this report" notice with the same (or at least, a very similar) crash. Mine wasn't on world creation though but the stacktrace is identical, if not very nearly.

Spawned in a jungle, same crash happened for me except with vines. 😞

Same problem here, with dark oak leaves. 14w30b

I also had this issue, but with both birch leaves and tall grass. See crash reports "crash-2014-07-23_16.55.48-client" and "crash-2014-07-23_13.37.58-client" respectively. The bug has something to do with tesselations. Confirmed for 14w30b.

Same thing as everyone else 14w30b ... sad because before the crash my frames are stunning! Can't wait for 1.8!

This can happen in an already-created world. I cannot find any immediate cause. Happens randomly as I go about my business exploring.

having the same problem, jungle logs and leaves, and the trees are generating with missing pieces, probably related

Same with me, it has the, your minecraft is modded cant accept crash. i was messing around sponge at the time...

That the Launcher is detecting Minecraft as modded is MC-63288

Got the same crash while flying around in creative. =3
You don't need another crash log, do you?

using the 14w30b snapshot

Same happens with me, most often when moving through the jungle.
It was unexplored terrain, I suspect it happens during world generation.

I'll move towards explored terrain and see if it still happens.

The launcher suspects I modded MC (I haven't) and therefor can't send the report directly to Mojang.
If you need more crash reports, I can produce them easily, unfortunately.
This crash makes playing the snapshot impossible, I hope you will push a 'c'.

I got this crash with a repeater and comperator today in less then a minute after each other, please fix, I can't work on my maps like this