When logging in to the Snapshot server, if you press "Cancel" while it's at the "Logging in..." phase, a NullPointerException will be thrown.
Steps to recreate;
1. Join a snapshot server
2. While "Logging in..." press cancel
---- Minecraft Crash Report ----
// Quite honestly, I wouldn't worry myself about that.
Time: 10/10/13 10:53 AM
Description: Exception in server tick loop
java.lang.NullPointerException
at mx.d(SourceFile:103)
at mx.a(SourceFile:95)
at mo.c(SourceFile:130)
at net.minecraft.server.MinecraftServer.u(SourceFile:528)
at lh.u(SourceFile:259)
at net.minecraft.server.MinecraftServer.t(SourceFile:440)
at net.minecraft.server.MinecraftServer.run(SourceFile:358)
at kw.run(SourceFile:616)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- System Details --
Details:
Minecraft Version: 13w41a
Operating System: Linux (amd64) version 2.6.32-358.18.1.el6.x86_64
Java Version: 1.7.0_25, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 1828113784 bytes (1743 MB) / 2137849856 bytes (2038 MB) up to 8580300800 bytes (8182 MB)
JVM Flags: 10 total; -Xms2G -Xmx8G -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ParallelGCThreads=2 -XX:+CMSParallelRemarkEnabled -XX:+DisableExplicitGC -XX:MaxGCPauseMillis=500 -XX:SurvivorRatio=16 -XX:TargetSurvivorRatio=90
AABB Pool Size: 1707 (95592 bytes; 0 MB) allocated, 1444 (80864 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
Profiler Position: N/A (disabled)
Vec3 Pool Size: 1294 (72464 bytes; 0 MB) allocated, 581 (32536 bytes; 0 MB) used
Player Count: 1 / 20; [mi['McMuffinn6'/3332, l='world', x=-472.33, y=106.00, z=226.09]]
Is Modded: Unknown (can't tell)
Type: Dedicated Server (map_server.txt)Linked issues
is duplicated by 9
MC-34803
Server Crash: java.lang.NullPointerException
Resolved
MC-35037
Hopper: java.lang.NullPointerException: Exception in server tick loop
Resolved
MC-35048
Hopper: java.lang.NullPointerException: Exception in server tick loop
Resolved
MC-35144
Server crash upon startup on 13w41a/b
Resolved
MC-35345
Hopper: java.lang.NullPointerException: Exception in server tick loop
Resolved
Attachments
Comments 14
This may have been fixed by my other issue - https://mojang.atlassian.net/browse/MC-34705
It appears to be fixed for me, so it may have been related to it.
Another crash with a slightly different crash report; same symptoms as in MC-34803. Crash report is attached.
Following is the relevant excerpt from the server log:
[18:36:11] [Netty IO #2/ERROR]: Channel became inactive!
[18:36:16] [Netty IO #3/ERROR]: Channel became inactive!
[18:36:21] [Netty IO #4/ERROR]: Channel became inactive!
[18:36:26] [Server thread/ERROR]: Encountered an unexpected exception
java.lang.NullPointerException
at ml.c(SourceFile:130) ~[minecraft_server.13w41b.jar:?]
at net.minecraft.server.MinecraftServer.u(SourceFile:529) ~[minecraft_server.13w41b.jar:?]
at le.u(SourceFile:259) ~[minecraft_server.13w41b.jar:?]
at net.minecraft.server.MinecraftServer.t(SourceFile:441) ~[minecraft_server.13w41b.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:358) [minecraft_server.13w41b.jar:?]
at kt.run(SourceFile:617) [minecraft_server.13w41b.jar:?]
[18:36:26] [Netty IO #5/ERROR]: Channel became inactive!
[18:36:26] [Server thread/ERROR]: This crash report has been saved to: /home/minecraft/Survival-Inc-13w36a/./crash-reports/crash-2013-10-15_18.36.26-server.txt
[18:36:31] [Netty IO #6/ERROR]: Channel became inactive!
[18:36:36] [Netty IO #7/ERROR]: Channel became inactive!
[18:36:41] [Netty IO #0/ERROR]: Channel became inactive!
Is this still a concern in the latest Minecraft version 13w48b? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
I have had three severs running 1.7.2 since it was released. I have not seen this problem, but I did see it on the snapshot versions just before the official release. I think the problem was only present in the snapshot versions.
My suggestion is to close this issue.
This ticket is invalid without the requested information, no response has been received within a reasonable time and we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.
Please attach crash reports to tickets, not to 3rd party file hoster.