Donna

Minecraft crashes to ios homescreen when loading the Jurassic World DLC, either a new world or a old world that had already been successfully played. We purchased the Jurassic World DLC a few years ago and had no problem with it until the 1.19 update for bedrock/ios edition. We are also having the same trouble on the PS4 version after updating. The latest patch has not seemed to fix the problem. The game just exits upon clicking to load the world. All other worlds
(that we have tried) are working as intended.

This is only when loading the Jurassic World DLC world template, as either a new world or existing world. Normal game and other DLC themed worlds run fine.

I also have the same issue after miss interperating what I was meant to do when first downloading minecraft for PS4. It asked me to log into a MS account and I could only do it once. Upon googling it and reading as much info as I could I came to the conclusion that only 1 MS can be linked to each PS4 so I linked my sons account to my PS4 profile (as I happened to be the one logged in). Then I realised later on when I set up a PS4 user for him that you actually CAN link more then 1 MS account to the PS4, they are just linked to your PS4 user (first time using PS here!) and now my sons MS account is linked to my PS4 account instead of his PS$ account. I contacted Minecraft support, who asked me to contact microsoft, who sent me back to mojang support who emailed me asking me to join this thread as they are looking into a way to unlink permanatly linked MS accounts to ps4 accounts but they do not have a timeframe when we will be able to do this. so for now I cannot play minecraft on my PS4 and my son has to play using my PS4 account.

Playstation and mojang need to have more information on the PS4 when asking to link an MS account to the Playstation Network that only 1 MS account can be linked to 1 PS4 account at a time, and not make it sound like the whole Ps4 and only 1 account for the whole system.

I've been reading through endless comments and trying everything to fix this error, I've been playing on my realm for two months now and I've NEVER had an issue. The only thing that seemed to work is connecting to my mobile hotspot which allows me to finally view my realm but when i switch back to normal wifi it no longer works.

This is still happening on 1.16.50 for IOS

I am also having this issue. I can see alot of problems when I search different forums with this issue dating back to 2018. It is the 17th of October 2020 and I am having this issuse. I am using Windows 10 Edition on a PC with a direct lan connection to the internet. It said in a message that my subscription has been activated but could not create a realm right now. Check back later. I have no issues connecting to someone else's realm, nor hosting a multiplayer or lan game.

The advice online is generally to get a refund and just do not have a realm. I just started the free 30 day trial so there is no refund to be had at the moment but they will start to charge me for the subscrption in 30 days.  I am not sure if this is the correct place to seek support but the Mojang website send me here.

Is this something you are going to look into or so I just cancel my subscription and forget about having a realm?

Kind regards,
Donna.

thanks. that seemed to work.

This is what else I get as well.

19:49:18 game error ---- Minecraft Crash Report ----
// Ouch. That hurt 😞

Time: 25/03/18 11:49 PM
Description: Initializing game

java.lang.OutOfMemoryError: Java heap space
at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75)
at java.awt.image.Raster.createPackedRaster(Raster.java:467)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1032)
at java.awt.image.BufferedImage.<init>(BufferedImage.java:340)
at cuj.a(SourceFile:407)
at cua.b(SourceFile:238)
at cua.a(SourceFile:77)
at cxh.j(SourceFile:553)
at cxh.a(SourceFile:139)
at cxk.a(SourceFile:23)
at cvt.a(SourceFile:99)
at bsu.aj(SourceFile:437)
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)

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

– Head –
Stacktrace:
at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75)
at java.awt.image.Raster.createPackedRaster(Raster.java:467)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1032)
at java.awt.image.BufferedImage.<init>(BufferedImage.java:340)
at cuj.a(SourceFile:407)
at cua.b(SourceFile:238)
at cua.a(SourceFile:77)
at cxh.j(SourceFile:553)
at cxh.a(SourceFile:139)
at cxk.a(SourceFile:23)
at cvt.a(SourceFile:99)
at bsu.aj(SourceFile:437)

– Initialization –
Details:
Stacktrace:
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)

– System Details –
Details:
Minecraft Version: 1.8
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 141639976 bytes (135 MB) / 1073741824 bytes (1024 MB) up to 1073741824 bytes (1024 MB)
JVM Flags: 8 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8
LWJGL: 2.9.1
OpenGL: AMD Radeon(TM) R5 Graphics GL version 4.5.13474 Compatibility Profile Context 22.19.163.1792, ATI Technologies Inc.
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: [[1.10]R3D+CRAFT+DR-512x(v0.1.5).zip]
Current Language: English (US)
Profiler Position: N/A (disabled)
#@

Crash report saved to: #@!@# C:\Users\theca\AppData\Roaming\.minecraft\crash-reports\crash-2018-03-25_23.49.18-client.txt
<log4j:Event logger="net.minecraft.server.MinecraftServer" timestamp="1522036158237" level="INFO" thread="Client Shutdown Thread">
<log4j:Message><![CDATA[Stopping server]]></log4j:Message>
</log4j:Event>
19:49:18 monitor Process Monitor error expected <

Ok guys! Something good just happened. We clicked out of/closed the stuck Minecraft main screen (looked just like Ricky's screenshot) and then clicked on the Minecraft icon to re-open it. Right away, a small box opened up in middle of screen and said something like 'updating Minecraft' and 'installing run-time'. Then, after about 45 seconds....voila'!! It's back up and running.

It appears that some type of update needed to occur.

All I can say is, keep trying to re-open it, to maybe get this update to initiate. I think that's what was/is causing our glitch.

We are also having this exact issue! We are on a Mac OS 10.11.6.
Have restarted the game, won't reinstall if JT says it didn't work.
If one of you find a solution, PLEASE post here? Or, email us at: [email protected]
SO frustrating...