Minecraft 1.13 Release Crashing

minecraft-java-editiontechnical-issues

Here's the crash report I keep receiving, it quits on launch of the game, has been working okay until pre-8 and has failed to load since then. If anyone can help that'd be wonderful. My resolution tab is turned off, the game directory is default, I am not running any mods.

---- Minecraft Crash Report ----
// Hey, that tickles! Hehehe!

Time: 7/18/18 10:45 PM
Description: Initializing game

java.lang.NullPointerException: Initializing game
    at cfi.am(SourceFile:475)
    at cfi.a(SourceFile:377)
    at net.minecraft.client.main.Main.main(SourceFile:144)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Client thread
Stacktrace:
    at cfi.am(SourceFile:475)

-- Initialization --
Details:
Stacktrace:
    at cfi.a(SourceFile:377)
    at net.minecraft.client.main.Main.main(SourceFile:144)

-- System Details --
Details:
    Minecraft Version: 1.13
    Operating System: Windows 10 (amd64) version 10.0
    Java Version: 1.8.0_51, Oracle Corporation
    Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
    Memory: 310029672 bytes (295 MB) / 570425344 bytes (544 MB) up to 1073741824 bytes (1024 MB)
    JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M
    Launched Version: 1.13
    LWJGL: 3.1.6 build 14
    OpenGL: Intel(R) HD Graphics 620 GL version 4.5.0 - Build 22.20.16.4836, Intel
    GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

Using VBOs: Yes
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: 
Current Language: ~~ERROR~~ NullPointerException: null
Profiler Position: N/A (disabled)
CPU: 4x Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz

Best Answer

I tried everything suggested but what finally worked for me was uninstalling java altogether and downloading the minecraft java edition from the minecraft website. hope it helps.

Related Solutions

Urban Terror not launching on OSX 10.9

seta r_ignorehwgamma "1"

You can add that line to your q3config.cfg. To edit it, open a new Finder window, hit cmd+shift+G, and paste ~/Library/Application Support/Quake3/q3ut4/ in the box, and when the folder opens, you'll see q3config.cfg. Just open that file with a text editor like TextEdit. If you don't have that file or folder (perhaps because you were trying to uninstall), open Terminal and enter:

<Full/Path/To/UrT>/Quake3-UrT.app/Contents/MacOS/Quake3-UrT.i386 +seta r_ignorehwgamma "1"

Hit enter and your game will launch with that setting.

So on my computer, that would be

/Applications/UrbanTerror4.2/Quake3-UrT.app/Contents/MacOS/Quake3-UrT.i386 +seta r_ignorehwgamma "1"

This bug apparently has to do with SDL and it seems unlikely that FrozenSand will upgrade their implementation to the newest version.

Setting r_ignorehwgamma "1" will disable in-game gamma/"brightness" controls, so you'll have to manually change it via System Preferences > Displays > Color > Calibrate. Once you create a new "high gamma" color profile, you can just click back and forth between it and your normal settings in the future.

Below is my original (and not very effective) answer...

I always get the deprecated call errors in Console every time I run Urban Terror, in Mavericks and even before Mavericks. It is NOT the source of the problem, nor is it a fatal error.

You CAN run Urban Terror under OS X 10.9 Mavericks. Those deprecated call errors can be ignored (for now at least). Anyone who says different is wrong :)

FIRST, as a potential shortcut, it may simply be a matter of toggling some settings in your config file. This doesn't work for everyone though.

Edit your q3config.cfg file:

On OS X, it's in /Users/~/Library/Application Support/Quake3/q3ut4/q3config.cfg

Open it in a text editor and find the line
seta r_fullscreen "1"
and toggle it off:
seta r_fullscreen "0"
You might also try setting r_mode "-1" and r_customwidth "1280" r_customheight "800"

If that doesn't fix it, follow these steps and hopefully you'll be able to launch the game again:

Clean up with Onyx

List item

Reboot into Recovery mode

Repair permissions

Repair disk Reboot normally and try to run Urban Terror

So, first you need to clean up your system.

You can do it manually, or automate the process with Onyx. I recommend all Mac users have Onyx installed, but if you don't want to, you can do it all manually. (...you'll have to find your own instructions though! Search for "OS X execute maintenance scripts manually" "OS X rebuild dyld's shared cache" and "OS X cleaning caches.")

Onyx will automate the process. You can get it by searching Google for "Titanium Onyx"

Once you've downloaded Onyx, run it and open the Automation tab. Check the following boxes:

This will close all running apps and it may take about 20 minutes or so to complete. When it's done, you will have to restart your computer. BEFORE you hit execute:

Save the following instructions somewhere if you can't remember them: After Onyx runs and you reboot, boot into Recovery mode by holding command+R. Once Recovery mode boots, open Disk Utility. Select your hard drive in the list and click the "Repair Permissions" button. Once that runs, click the "Repair disk" button. When that finishes, reboot and see if Urban Terror will run.

Okay, now that you have all the instructions, hit Execute in Onyx and start the process.

I took all of these steps at the same time, I still don't know exactly what the cause is, but my theory is that there is some cached data in the GL driver cache that is messing with the game. Once you clean the system/user caches, you should be good... but may as well do a full cleanup and repair permissions and the disk in Recovery mode, just to be sure.

Minecraft crashes on launch

This looks like a Minecraft bug, you should post it on the bug tracker (you'll have to create account for that)

Meanwhile, try to change the JVM locale from the Minecraft launcher:

Click on 'Installations' at the top
Click on the the version you are playing (it will probably say 'Latest release')
Click on 'More options'
In the 'JVM Arguments' field add -Duser.language=en-US. Make sure you do not change the other arguments and that what you are adding is separated from them with a space.

If that does not work for some reason, check if you can change your Windows locale to English. This may break other programs on your computer though.