MC-34617Animation crash if frame #0 is not referenced
A crash occurs if a resourcepack has an animation that does not reference frame #0 in its mcmeta file.
The attached resourcepack reproduces the problem. stone.png is 16x48 (3 frames), but stone.png.mcmeta uses only frames 1 and 2. Selecting this resource pack causes the game to crash while stitching blocks.png. Crash report also attached.
Environment
Fedora 19
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
Linked Issues
is duplicated by1
Created Issue:
Animation crash if frame #0 is not referenced
A crash occurs if a resourcepack has an animation that does not reference frame #0 in its mcmeta file.
The attached resourcepack reproduces the problem. stone.png is 16x48 (3 frames), but stone.png.mcmeta uses only frames 1 and 2. Selecting this resource pack causes the game to crash while stitching blocks.png. Crash report also attached.
Environment
Fedora 19
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
Attachments2
is duplicated by
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Your Java version is out of date! Please update your Java to the latest version: http://www.java.com/en/download/ .
Retested with Java 1.7.0_40, same result. Also confirmed with 13w41a.
Is this still a concern in the latest Minecraft version 13w48b? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
The game doesn't crash anymore in 13w48b, the animation just stops at frame 3 (tested with attached zip-file).
Marked as fixed.