Having creative inventory window open on a client when the server is (gracefully) stopped, causes a crash on the client. It does not happen with the survival inventory window.
What I expected to happen was..:
The "Disconnected by Server: Server Closed" message appears on the dirt background
What actually happened was...:
Client crash (see attached)
Steps to reproduce:
Start the server.
Login and switch to creative mode.
Open the creative inventory window and leave it open.
Stop the server.
Client crashes.
Linked issues
Attachments
Comments 5
Josh, what environment are you running? Perhaps it is specific to an OS or JRE version? It happens every time for me, but I'm not too worried about it as the simple workaround is to close the inventory window before the server stops 🙂
I can try some more tests on alternate OS and JRE versions tonight.
I'm not on my desktop at the moment, but it should be running with an up-to-date Sun JRE 7 (Windows 7) – I can get a more exact JRE version in the morning.
Bug replicated in 1.4.2 both with a fresh new server and a server with a modified world.
Mine is on Windows 7 64 bit, JRE7 (1.7.0_07). Will test on OS X.
Crash report:
---- Minecraft Crash Report ----
// I blame Dinnerbone.
Time: 10/25/12 4:15 PM
Description: Unexpected error
java.lang.NullPointerException
at aud.b(SourceFile:256)
at net.minecraft.client.Minecraft.a(SourceFile:433)
at awr.a(SourceFile:484)
at db.a(SourceFile:27)
at bx.b(SourceFile:341)
at awr.d(SourceFile:98)
at awz.b(SourceFile:61)
at net.minecraft.client.Minecraft.l(SourceFile:1282)
at net.minecraft.client.Minecraft.J(SourceFile:582)
at net.minecraft.client.Minecraft.run(SourceFile:534)
at java.lang.Thread.run(Unknown Source)
Relevant Details:
- Minecraft Version: 1.4.2
- Operating System: Windows 7 (amd64) version 6.1
- Java Version: 1.7.0_07, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 443009560 bytes (422 MB) / 514523136 bytes (490 MB) up to 954466304 bytes (910 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- AABB Pool Size: 14643 (820008 bytes; 0 MB) allocated, 721 (40376 bytes; 0 MB) used
- LWJGL: 2.4.2
- OpenGL: Intel(R) HD Graphics 4000 GL version 3.3.0 - Build 8.15.10.2696, Intel
- Is Modded: Probably not
- Type: Client
- Texture Pack: Default
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: ~ERROR~ NullPointerException: nullHm, I lied. I crashed it this time. Confirmed.
Open server, open client, connect, set gamemode to creative via console, open inventory, stop server from console.
Minecraft has crashed!
----------------------
Minecraft has stopped running because it encountered a problem; Unexpected error
This error has been saved to C:\Users\Josh\AppData\Roaming\.vanilla\.minecraft\crash-reports\crash-2012-10-25_01.37.25-client.txt for your convenience. Please include a copy of this file if you report this crash to anyone.
--- BEGIN ERROR REPORT 82627170 --------
Generated 10/25/12 1:37 AM
- Minecraft Version: 1.4.2
- Operating System: Windows 7 (amd64) version 6.1
- Java Version: 1.7.0_06, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 78675120 bytes (75 MB) / 143196160 bytes (136 MB) up to 1905197056 bytes (1816 MB)
- JVM Flags: 0 total;
- AABB Pool Size: 5246 (293776 bytes; 0 MB) allocated, 225 (12600 bytes; 0 MB) used
- LWJGL: 2.4.2
- OpenGL: GeForce GTX 580/PCIe/SSE2 GL version 4.2.0, NVIDIA Corporation
- Is Modded: Probably not
- Type: Client
- Texture Pack: Default
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: ~ERROR~ NullPointerException: null
java.lang.NullPointerException
at aud.b(SourceFile:256)
at net.minecraft.client.Minecraft.a(SourceFile:433)
at awr.a(SourceFile:484)
at db.a(SourceFile:27)
at bx.b(SourceFile:341)
at awr.d(SourceFile:98)
at awz.b(SourceFile:61)
at net.minecraft.client.Minecraft.l(SourceFile:1282)
at net.minecraft.client.Minecraft.J(SourceFile:582)
at net.minecraft.client.Minecraft.run(SourceFile:534)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 634c0a58 ----------
I cannot reproduce this in 1.4.2.