After closing minecraft, the following error is in the development console.
Client> java.io.IOException: Stream Closed
Client> at java.io.RandomAccessFile.seek(Native Method)
Client> at aos.a(SourceFile:308)
Client> at aos.a(SourceFile:251)
Client> at aot.close(SourceFile:232)
Client> at java.util.zip.DeflaterOutputStream.close(Unknown Source)
Client> at java.io.FilterOutputStream.close(Unknown Source)
Client> at aov.a(SourceFile:145)
Client> at aov.c(SourceFile:133)
Client> at ayc.b(SourceFile:30)
Client> at ayc.run(SourceFile:23)
Client> at java.lang.Thread.run(Unknown Source)
Client> [16:12:49] [Server thread/INFO]: Saving chunks for level 'Minecraft'/Nether
Client> [16:12:49] [Server thread/INFO]: Saving chunks for level 'Minecraft'/The End
Client> [16:12:55] [Client thread/INFO]: Stopping!
The error is only shown in the development console not in the latest log:
[16:12:49] [Server thread/INFO]: Saving chunks for level 'Minecraft'/Overworld
[16:12:49] [Server thread/INFO]: Saving chunks for level 'Minecraft'/Nether
[16:12:49] [Server thread/INFO]: Saving chunks for level 'Minecraft'/The End
[16:12:55] [Client thread/INFO]: Stopping!
Related issues
is duplicated by
Comments
Is this still a concern in the current Minecraft version 14w10c / Launcher version 1.3.10 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Is this still a concern in the current Minecraft version 14w18b / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
When shutting down 14w20b on Ubuntu, there are several hundred of these errors that fill the scroll back buffer, pushing off any previous messages:
[23:13:41 ERROR]: java.io.IOException: Stream closed
galaxy_2alex
Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
marcono1234
Duplicates MC-10976
Is this still a concern in the current Minecraft version 1.7.4 / Launcher version 1.3.7 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.