-
Bug
-
Resolution: Duplicate
-
None
-
Minecraft 1.12 Pre-Release 2
-
None
-
Windows 10 x64 (Using the Java 1.8.0_25 runtime)
-
Unconfirmed
Noticed this problem since this prerelease, if a server does not respond to the pinger, it crashes the client.
00:29:38 bsc Can't ping 62.210.196.215:25092: Timed out
00:29:39 bhv Reported exception thrown!
f: Ticking screen
at bhv.t(SourceFile:1607)
at bhv.ax(SourceFile:965)
at bhv.a(SourceFile:405)
at net.minecraft.client.main.Main.main(SourceFile:123)
Caused by: java.lang.NullPointerException
at io.netty.bootstrap.Bootstrap.checkAddress(Bootstrap.java:358)
at io.netty.bootstrap.Bootstrap.doResolveAndConnect(Bootstrap.java:180)
at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:162)
at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:143)
at bsc.b(SourceFile:241)
at bsc.a(SourceFile:45)
at bsc$1.a(SourceFile:144)
at gw.l(SourceFile:382)
at bsc.a(SourceFile:254)
at bmz.e(SourceFile:115)
at bhv.t(SourceFile:1597)
... 3 more
This issue happens when the request times out so the client crashes. Happens with desteria's server and someone's server which does not respond to the pinger.
PS: I've tried searching if someone reported that issue and I couldn't find it.
- duplicates
-
MC-108343 Minecraft crashes with "java.lang.NullPointerException: Ticking screen" while pinging server on multiplayer server list (previously due to network issues, now more frequent)
- Resolved