mojira.dev

xPaw

Assigned

No issues.

Reported

View all

Comments

Why was this closed as 'working as intended'?

Java VM still crashes in 1.8-pre2. This affects multiplayer as well.

Change affected version please.

It's still crashing in 1.8-pre1 on intel gpu.
Log: https://gist.github.com/xPaw/fa34a29abec61ba3cbdc

It's still crashing in 1.8-pre1 on intel gpu.

Log: https://gist.github.com/xPaw/fa34a29abec61ba3cbdc

No, they are not outdated. This only happens whenever joining a multiplayer server (and even then, not always).

I still don't understand why it displays a stacktrace. Instead it should say a new empty file will be created (more user friendly).

This issue was marked as fixed in Minecraft 14w10b, but it still displays same message (with stacktrace) in 'b' snapshot.

This is still happening on latest snapshot.

[14:34:09] [Server Listen Thread/ERROR]: Exception handling pending connection
java.net.SocketException: Socket closed
        at java.net.PlainSocketImpl.socketAccept(Native Method) ~[?:1.7.0_25]
        at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) ~[?:1.7.0_25]
        at java.net.ServerSocket.implAccept(ServerSocket.java:530) ~[?:1.7.0_25]
        at java.net.ServerSocket.accept(ServerSocket.java:498) ~[?:1.7.0_25]
        at jt.run(SourceFile:66) [minecraft_server.jar:?]
[14:34:09] [Server Listen Thread/ERROR]: Exception handling pending connection
java.net.SocketException: Socket closed
        at java.net.PlainSocketImpl.socketAccept(Native Method) ~[?:1.7.0_25]
        at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) ~[?:1.7.0_25]
        at java.net.ServerSocket.implAccept(ServerSocket.java:530) ~[?:1.7.0_25]
        at java.net.ServerSocket.accept(ServerSocket.java:498) ~[?:1.7.0_25]
        at jt.run(SourceFile:66) [minecraft_server.jar:?]

Can confirm, these exceptions happen from time to time on a server.

[06:27:26] [Connection #107 read thread/ERROR]: Exception on tcp connection
java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method) ~[?:1.7.0_25]
        at java.net.SocketInputStream.read(SocketInputStream.java:150) ~[?:1.7.0_25]
        at java.net.SocketInputStream.read(SocketInputStream.java:121) ~[?:1.7.0_25]
        at java.net.SocketInputStream.read(SocketInputStream.java:203) ~[?:1.7.0_25]
        at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:288) ~[?:1.7.0_25]
        at gw.a(SourceFile:180) ~[minecraft_server.jar:?]
        at ec.j(SourceFile:251) [minecraft_server.jar:?]
        at ec.c(SourceFile:19) [minecraft_server.jar:?]
        at ed.run(SourceFile:96) [minecraft_server.jar:?]
[06:27:26] [Connection #107 read thread/ERROR]: Exception on tcp connection
java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method) ~[?:1.7.0_25]
        at java.net.SocketInputStream.read(SocketInputStream.java:150) ~[?:1.7.0_25]
        at java.net.SocketInputStream.read(SocketInputStream.java:121) ~[?:1.7.0_25]
        at java.net.SocketInputStream.read(SocketInputStream.java:203) ~[?:1.7.0_25]
        at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:288) ~[?:1.7.0_25]
        at gw.a(SourceFile:180) ~[minecraft_server.jar:?]
        at ec.j(SourceFile:251) [minecraft_server.jar:?]
        at ec.c(SourceFile:19) [minecraft_server.jar:?]
        at ed.run(SourceFile:96) [minecraft_server.jar:?]

It's not throwing an exception anymore, but it still launches minecraft (after closing the launcher).

There's also another exception 2 seconds later, here's the log:

2013-05-10 23:16:15 [SEVERE] Reached end of stream
2013-05-11 09:16:59 [SEVERE] Reached end of stream
2013-05-11 09:17:05 [INFO] **** logged in with entity id 151 at (2.5511040892606154, 66.0, -25.62285088069156)
java.lang.NullPointerException
        at ek.a(SourceFile:231)
        at fh.a(SourceFile:50)
        at ek.a(SourceFile:222)
        at ck.h(SourceFile:182)
        at ck.d(SourceFile:16)
        at cm.run(SourceFile:115)
2013-05-11 09:17:05 [INFO] **** lost connection: disconnect.genericReason
2013-05-11 09:17:05 [INFO] **** lost connection: disconnect.genericReason
2013-05-11 09:17:07 [SEVERE] Reached end of stream
java.lang.IllegalArgumentException: Empty string not allowed
        at cg.<init>(SourceFile:15)
        at bu.a(SourceFile:77)
        at asc.e(SourceFile:186)
        at asc.b(SourceFile:112)
        at alj.a(SourceFile:88)
        at alj.a(SourceFile:76)
        at jb.a(SourceFile:646)
        at jb.a(SourceFile:631)
        at net.minecraft.server.MinecraftServer.a(SourceFile:265)
        at net.minecraft.server.MinecraftServer.r(SourceFile:412)
        at net.minecraft.server.MinecraftServer.run(SourceFile:341)
        at gr.run(SourceFile:584)
2013-05-10 23:16:15 [SEVERE] Reached end of stream
2013-05-11 09:16:59 [SEVERE] Reached end of stream
2013-05-11 09:17:05 [INFO] **** logged in with entity id 151 at (2.5511040892606154, 66.0, -25.62285088069156)
java.lang.NullPointerException
        at ek.a(SourceFile:231)
        at fh.a(SourceFile:50)
        at ek.a(SourceFile:222)
        at ck.h(SourceFile:182)
        at ck.d(SourceFile:16)
        at cm.run(SourceFile:115)
2013-05-11 09:17:05 [INFO] **** lost connection: disconnect.genericReason
2013-05-11 09:17:05 [INFO] **** lost connection: disconnect.genericReason
2013-05-11 09:17:07 [SEVERE] Reached end of stream
java.lang.IllegalArgumentException: Empty string not allowed
        at cg.<init>(SourceFile:15)
        at bu.a(SourceFile:77)
        at asc.e(SourceFile:186)
        at asc.b(SourceFile:112)
        at alj.a(SourceFile:88)
        at alj.a(SourceFile:76)
        at jb.a(SourceFile:646)
        at jb.a(SourceFile:631)
        at net.minecraft.server.MinecraftServer.a(SourceFile:265)
        at net.minecraft.server.MinecraftServer.r(SourceFile:412)
        at net.minecraft.server.MinecraftServer.run(SourceFile:341)
        at gr.run(SourceFile:584)

It's not throwing an exception anymore, but it leaves the process and launches Minecraft regardless.

It still teleports you, and you get stuck.