WorldClient leaked by static reference in PrimitiveMobsParticles
mjdg opened this issue ยท 2 comments
The static initializer for PrimitiveMobsParticles caches a reference to the current WorldClient which is never released, leaking memory. Steps to reproduce:
- create a single-player world
- spawn a TreasureSlime to make sure the static initializer is called (I think - my Java ain't too good!)
- quit to main menu
- reload the save from step 1
Examining the heap e.g. with VisualVM shows two WorldClient objects, the second of which is referenced by the Minecraft object and the first by PrimitiveMobParticles.theWorld.