Dynamically changing parts of blocks are not disappearing when they're no longer rendered

The old chest model didn't disappear and can bee seen by opening the chest. after breaking the sorce chest, you can place blocks in the ghost chest

The old chest model didn't disappear and can bee seen by opening the chest. after breaking the sorce chest, you can place blocks in the ghost chest

Confirmed for 14w30c

Relating (or duplicating) MC-62350

If my bug is relating to another one that is obviously the one that represents this issue, do I close mine? I think I figured the bug out, Blocks with smoothly moving parts (the book of an enchantment table) or that are visually affected by their Tile Entity (text on a sign) are failing to remove their rendered moving, or changing parts after being no longer loaded. Anyway, here's a forced crash where the bug was happening with a few different blocks if it helps (not that you couldn't get it yourself and I don't see anything useful in there either)

---- Minecraft Crash Report ----
// I just don't know what went wrong :(

Time: 7/30/14 11:41 AM
Description: Manually triggered debug crash

java.lang.Throwable
	at brp.r(SourceFile:1565)
	at brp.ar(SourceFile:871)
	at brp.a(SourceFile:311)
	at net.minecraft.client.main.Main.main(SourceFile:120)


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

-- Head --
Stacktrace:
	at ccz.a(SourceFile:308)

-- Affected level --
Details:
	Level name: MpServer
	All players: 1 total; [cha['lewmas'/0, l='MpServer', x=22.43, y=56.00, z=303.51]]
	Chunk stats: MultiplayerChunkCache: 361, 361
	Level seed: 0
	Level generator: ID 01 - flat, ver 0. Features enabled: false
	Level generator options: 
	Level spawn location: 23.00,4.00,303.00 - World: (23,4,303), Chunk: (at 7,0,15 in 1,18; contains blocks 16,0,288 to 31,255,303), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
	Level time: 5236 game time, 5236 day time
	Level dimension: 0
	Level storage version: 0x00000 - Unknown?
	Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
	Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: false
	Forced entities: 1 total; [cha['lewmas'/0, l='MpServer', x=22.43, y=56.00, z=303.51]]
	Retry entities: 0 total; []
	Server brand: vanilla
	Server type: Integrated singleplayer server
Stacktrace:
	at ccz.a(SourceFile:308)
	at brp.b(SourceFile:2254)
	at brp.a(SourceFile:320)
	at net.minecraft.client.main.Main.main(SourceFile:120)

-- System Details --
Details:
	Minecraft Version: 14w30c
	Operating System: Windows 8.1 (amd64) version 6.3
	Java Version: 1.7.0_55, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 444011336 bytes (423 MB) / 745013248 bytes (710 MB) up to 2863661056 bytes (2731 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx3G
	IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
	Launched Version: 14w30c
	LWJGL: 2.9.1
	OpenGL: Intel(R) HD Graphics GL version 4.0.0 - Build 10.18.10.3308, Intel
	GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

	Using VBOs: Yes
	Is Modded: Probably not. Jar signature remains and client brand is untouched.
	Type: Client (map_client.txt)
	Resource Packs: []
	Current Language: English (US)
	Profiler Position: N/A (disabled)

If my bug is relating to another one that is obviously the one that represents this issue, do I close mine? I think I figured the bug out, Blocks with smoothly moving parts (the book of an enchantment table) or that are visually affected by their Tile Entity (text on a sign) are failing to remove their rendered moving, or changing parts after being no longer loaded. Anyway, here's a forced crash where the bug was happening with a few different blocks if it helps (not that you couldn't get it yourself and I don't see anything useful in there either)

---- Minecraft Crash Report ----
// I just don't know what went wrong :(

Time: 7/30/14 11:41 AM
Description: Manually triggered debug crash

java.lang.Throwable
	at brp.r(SourceFile:1565)
	at brp.ar(SourceFile:871)
	at brp.a(SourceFile:311)
	at net.minecraft.client.main.Main.main(SourceFile:120)


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

-- Head --
Stacktrace:
	at ccz.a(SourceFile:308)

-- Affected level --
Details:
	Level name: MpServer
	All players: 1 total; [cha['lewmas'/0, l='MpServer', x=22.43, y=56.00, z=303.51]]
	Chunk stats: MultiplayerChunkCache: 361, 361
	Level seed: 0
	Level generator: ID 01 - flat, ver 0. Features enabled: false
	Level generator options: 
	Level spawn location: 23.00,4.00,303.00 - World: (23,4,303), Chunk: (at 7,0,15 in 1,18; contains blocks 16,0,288 to 31,255,303), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
	Level time: 5236 game time, 5236 day time
	Level dimension: 0
	Level storage version: 0x00000 - Unknown?
	Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
	Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: false
	Forced entities: 1 total; [cha['lewmas'/0, l='MpServer', x=22.43, y=56.00, z=303.51]]
	Retry entities: 0 total; []
	Server brand: vanilla
	Server type: Integrated singleplayer server
Stacktrace:
	at ccz.a(SourceFile:308)
	at brp.b(SourceFile:2254)
	at brp.a(SourceFile:320)
	at net.minecraft.client.main.Main.main(SourceFile:120)

-- System Details --
Details:
	Minecraft Version: 14w30c
	Operating System: Windows 8.1 (amd64) version 6.3
	Java Version: 1.7.0_55, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 444011336 bytes (423 MB) / 745013248 bytes (710 MB) up to 2863661056 bytes (2731 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx3G
	IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
	Launched Version: 14w30c
	LWJGL: 2.9.1
	OpenGL: Intel(R) HD Graphics GL version 4.0.0 - Build 10.18.10.3308, Intel
	GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

	Using VBOs: Yes
	Is Modded: Probably not. Jar signature remains and client brand is untouched.
	Type: Client (map_client.txt)
	Resource Packs: []
	Current Language: English (US)
	Profiler Position: N/A (disabled)

Confirmed for

• 14w31a

Confirmed for Beacons as well. MC-66623

Confirmed for Beacons as well. MC-66623

All of these bugs are part of MC-62166

At least related.

The way I see it is that because this bug is completely visual, and reloading the chunk solves it, it definitely acts the same as MC-62166 and F3+A always fixes this bug. It would be better to point the entire community towards one report, and increase the votes than to split up 2 of the same issue simply because one affects movable blocks and the other doesn't. If MC-62166 gets fixed and this doesn't (I highly doubt they are different), this one can be reopened. But it would be better to merge them and create one report.

Affects 14w34b

Affects 14w34b