MC-46338java.io.IOException: Bad file descriptor
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)
-------------------
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.
Environment
OSX 10.6
Linked Issues
is duplicated by1
Created Issue:
java.io.IOException: Bad file descriptor
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)-------------------
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.
Environment
OSX 10.6
is duplicated by
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
After some research, I found the cause: It's a Java bug, not a Minecraft bug. You're lucky, usually this can cause crashes on servers or similar.
The Minecraft Singleplayer console might simply ignore this error, as it doesn't seem to cause any damage an in your case, so it's probably only viewable with a special console.
In case you are interested: http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml
This should not be closed as 'invalid'. Although the page you linked to talks about what is probably a related issue, I don't believe it's the same as what I'm seeing. For one, that bug was resolved five years ago in Java 1.5 (whereas OSX 10.6 comes with Java 1.6). Secondly, the page you linked to implies that this was a pseudo randomized error that would pop up in multiple places. What I'm seeing is this EXACT same error, same text, character for character, every single time, and it's always and only after a chunk save operation.
Please reopen this bug (I apparently do not have permission to do so). This is NOT the same 'bug in Java' as what you linked to, as that was fixed by Sun back in 2007. What I'm seeing is obviously something else.