Maps will be kept in memory even after disconnecting from a server.
Proof: https://youtu.be/2vcMEGn4IgI ( 1Min 32 Sec )
The Video shows multiple reconnects to a Server resulting in a OutOfMemoryError with Vanilla 1.8.6
The only possible workaround is to restart the Minecraft-Client.
This is related to MC-46345 ( MC-80297 ) and might be caused by the same faulty code - but the bug in itself is different.
Update
This issue is not fixed in 1.9.2.
Proof: https://www.youtube.com/watch?v=biQF9qu2ww8
MC-46345 only refers to the maps no longer updating.
This report refers to the memory never being cleared and ultimately causing a OutOfMemoryError.
Related issues
Attachments
Comments


Might be related to MC-80608

Probably fixed, see MC-88349

Resolving to MC-88349, let us know if it isn't fixed in the snapshots.

This issue is not fixed in 1.9.2.
https://www.youtube.com/watch?v=biQF9qu2ww8
MC-46345 only refers to the maps no longer updating.
This report refers to the memory never being cleared and ultimately causing a OutOfMemoryError.

Reopened, make sure the description is up to date.

Can you please provide a way to reproduce, for example a server world which loads these maps?

Sorry I dont understand you comment. None of your reports are even related to client-side memoryleaks and maps. For this Bug it does not matter what server you join. Just join random Servers with maps for some time and your client will crash at some point.

Never mind, sorry for that. I though that the redstone toggle state map would contain the client world the client creates for the server loaded and because of this the maps as well.

Looks like this is caused by MC-98707

@unknown Does this still happen, in 1.10.2 as well as in the latest 1.11 snapshot (16w44a)?
I can only test in Singleplayer worlds at the moment.

As far as i can tell this was fixed with https://bugs.mojang.com/browse/MC-46345
Every version above 16w42a should be fixed currently. Thus 1.10.2 should still have the problem.