java.io.IOException: Bad file descriptor
at java.io.RandomAccessFile.seek(Native Method)
at aoy.a(SourceFile:308)
at aoy.a(SourceFile:251)
at aoz.close(SourceFile:232)
at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:143)
at java.io.FilterOutputStream.close(FilterOutputStream.java:143)
at apb.a(SourceFile:145)
at apb.c(SourceFile:133)
at ayi.b(SourceFile:30)
at ayi.run(SourceFile:23)
at java.lang.Thread.run(Thread.java:680)
-------------------
NOTE:
Please do not link to 'http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml' and claim that this is 'a bug in Java'. That bug was patched back in 2007 for Java 1.5, whereas I am running 1.6.
Please also do not mark this as a duplicate of 46338.
-------------------
I see this error a LOT when messing around in SSP. It appears immediately after 'Saving chunks for level', about 15% of the times I run the program (121 out of 843). I've yet to notice any world or player data corruption. There's no rhyme or reason for when it happens vs not, and I can't reproduce it on demand. IIRC this also used to happen on 1.6.x (but I can't verify that at the moment). I've verified that my disk is OK via both DiskUtility and SMART.
Note: I'm using a custom java console log divert thing to see these. These errors are trapped from Minecraft's output stream, but Minecraft itself apparently does not write them into its own logs. Given this and that the error mentions zip, I'm guessing the problem lies somewhere with archiving and shuffling the logs around.
Linked issues
Comments 4
We don't KNOW if it's causing problems or not. There's always a possibility of silent corruption or some other issue. And seriously, where do you get off saying "you're not supposed to see it"?? How do you know this isn't a compound problem that's preventing the error from showing up there when it should? Problems aren't going to get fixed if you just plug your ears and scream "LA LA LA I CAN'T HEAR YOU"
Please reopen this bug so someone at Mojang can ACTUALLY investigate the issue and see what's happening. Don't just up and decide that something's not a problem on a whim.
If this is not causing any problems, then it's not a problem... If you can't see it in the regular Minecraft console, you are not supposed to see it.
Duplicate of MC-46338