Memory leak in TickingTracker

Matrix4f.invert is broken

Block entity ticking checks chunk (target) ticket level instead of actual chunk ticking state when checking for ticking chunk, resulting in block entities being sometimes ticked in border chunks

Launcher randomly quits

Mushroom generation very rare due to light check with no light calculated while placing mushroom feature

Minecraft uses several times more VRAM than needed after exploring terrain for a while

Setting render distance to values >8 chunks freezes the game for >1 second (minutes for higher values)

Minecraft will remove up to several hundred chunks per region if region file isn't exact multiple of 4096 bytes

Teleporting big distance freezes the server

Minecraft keeps previously used World in memory if the player has hit any entity in that world

Watchdog thread kills the server if average tick time is larger than max-tick-time/(15*20) ms for too long

Chunks not rendering at certain positions when joining server where the chunks have been already loaded

Parts of area under blocks set with /fill are still fully lit clientside

Possible rare concurrency issue may cause changes in chunk to be reverted

Rendering empty chunks/cubes in 14w29b (or number of rendered chunks on debug screen (C) is wrong)