mojira.dev
MC-191157

Crash when trying to open Minecraft Realms screen - java.lang.NullPointerException: Rendering screen

Moderator Note

Realms is currently experiencing some issues, the only recommendation we can give at this moment is to avoid it until the issues are fixed.

Update: Mojang is aware and is trying their best to fix it: https://twitter.com/MojangStatus/status/1275450499949457408

When I am on the menu screen for minecraft for longer than a minute it crashes the game.

Here is the crash report:

Description: Rendering screen

java.lang.NullPointerException: Rendering screen
	at nd.a(SourceFile:27)
	at mr.b(SourceFile:109)
	at mr.a(SourceFile:76)
	at dmh.a(SourceFile:134)
	at dmi.a(SourceFile:42)
	at dmt.a(SourceFile:317)
	at dmv.a(SourceFile:117)
	at djv.a(SourceFile:67)
	at ebs.a(SourceFile:603)
	at dlx.e(SourceFile:1021)
	at dlx.e(SourceFile:654)
	at net.minecraft.client.main.Main.main(SourceFile:215)

Linked issues

MC-14430 I happens alot and it says something about Java Resolved MC-191159 Menu regarding realms crashes Resolved MC-191160 Trying to view Realms crashes game Resolved MC-191162 Blank Realms screen & game crashes after a minute Resolved MC-191163 Opening realms menu in 1.16 crashes the gaame. Resolved

Attachments

Comments 35

Was this on the Realms screen or the actual main menu?

From the main menu, I click to open Realms, and it never renders the Realms screen, just crashes after about 30 seconds or so.

I am having the same issues as Andrew Coffey it just crashes

This happened to me too. When it did load, it gave me the pop-up to buy a realm, and did not show the realms I was already a part of. One time they did load, but when I tried connecting to them I got the error: Realms (500) Could not connect to Realms: Read timed out

I also get this on the main launcher screen when it reopens after the crash:

[media]
25 more comments

Those are all different errors, as long as the game doesn't crash, it's good.

Confirmed, have the same behavior.

[media]

@Nik: That is not a crash, that is a connection error.

Never said it was a crash, just confirmed the behavior from the previous comment of Noah.

Still getting alternating 500, 502, and 504 errors. One time it gave me a 504 error, I hit "ok", then it thought for a bit and loaded the game. I played for a bit, wasn't kicked, logged out of Realms to see if I could log back in and not lose any progress, and then got the 500 & 504 error again.

Not sure if this matters or not, but the 'screen shot' for my Realm shows an image of a mini-game, even though up until the 1.16 update we've been playing in a world and not a mini-game. (It also takes FOREVER to load the Realm World thumbs under Configure World.)

underminerman

(Unassigned)

Community Consensus

Crash

1.16

1.16

Retrieved