Jon Atkins
Assigned
Reported
Comments
Also seeing this crash, after installing on a pretty new windows 7 64 bit install.
As the above commenter states, launcher crashes when exiting the game, but not when closed before a game launch. Nothing relevant in any of the log files.
Problem signature:
Problem Event Name: APPCRASH
Application Name: MinecraftLauncher.exe
Application Version: 1.0.1.0
Application Timestamp: 5af1959b
Fault Module Name: launcher.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5af19317
Exception Code: c0000005
Exception Offset: 00021b7e
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Not quite sure this is a duplicate of MC-38565, but since the Java upgrade (details above) it has been stable.
Also, the java upgrade fixed a separate issue I occasionally saw - 100% CPU usage on the server, when idle and no users connected.
I hadn't noticed earlier, but I also had that 'netty' warning message.
Also, since yet another crash, I decided to update Java - from the OpenJDK 1.6 to Oracle's 1.7
$ java -version
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
I'll keep a close eye on things and see if the issue still occurs.
More details. Just checked syslog, and found the following relating to excessive RAM usage for the two crashes today:
Nov 9 17:38:54 xev2 kernel: [992050.234014] Out of memory: Kill process 5646 (java) score 849 or sacrifice child
Nov 9 17:38:54 xev2 kernel: [992050.234063] Killed process 5646 (java) total-vm:4674276kB, anon-rss:1798104kB, file-rss:0kB
Nov 9 23:12:00 xev2 kernel: [1011997.750309] Out of memory: Kill process 4277 (java) score 823 or sacrifice child
Nov 9 23:12:00 xev2 kernel: [1011997.750350] Killed process 4277 (java) total-vm:4941608kB, anon-rss:1697984kB, file-rss:0kB
Minecraft server is the only java process running on the machine.
Before the crash occurs, there's no warning signs RAM is running tight, suggesting that when it goes wrong it happens quickly.
I've not yet found a way to reproduce it reliably. However, the two crashes today were after my brother logged in, found it was night, and immediately slept in a bed.
Also, $ java -version
java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.2)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
I've seen something similar on my server here.
I have a private server, used by myself and my brother, running on Ubuntu 12.04 LTS. The server machine is a VM with 2GB RAM allocated to it. A few other things are running too (e.g. webserver), but nothing high load.
The minecraft server is started with the command line "java -Xincgc -Xmx1024M -jar minecraft_server.jar nogui"
The first problems I noticed were severe issues on the server - so bad I couldn't log in. It appeared as if something was swapping like mad, causing the problem. The swap size was vastly reduced (from 4GB to 512MB) to limit swapping issues.
Now (and twice so far today), the minecraft process has crashed with the 'Killed' message. There are signs that RAM usage was high just before the crash, with some swapping - but I haven't yet managed to catch it in the act.
SRV lookups are failing for me. I'm running on Windows 7 64 bit with the standard Oracle (who bought Sun?) Java installation.
Versions installed are (from control panel, add/remove programs):
Java 7 Update 7 (64 bit) - version 7.0.70
Java 7 update 11 - version 7.0.110
Java SE Development Kit 7 Update 7 (64-bit) - ver 1.7.0.70
From the Minecraft snooper settings page, the java_version value is 1.7.0_07
Confirmed new in 1.4.3 - never seen it before.
However, unlike the MC-515 description, this DOES fix itself by logging out and in.
Confirmed in the 1.4.3 prerelease. On a private SMP server, the torch briefly appears in the correct location, then reappears on a different surface. Placing on the ground is the hardest - this will only work when all four other surfaces around the torch are unsuitable.
I've not tested on single player.
Confirmed. Attached is a screenshot of one in a jungle.
Fresh world created in 1.4.2, seed and coordinates shown.
Found https://bugs.mojang.com/browse/MCL-9319, so this should be marked as a duplicate