# Native memory allocation (mmap) failed to map 7733248 bytes for offset table expansion # An error report file with more information is saved as: # USERSDIR\Instances\JourneytotheCore\hs_err_pid12804. Loading Language: English Loading Language: English ATLauncher Version: 3.2.3.1 Operating System: Windows 8 RAM Available: 6040MB Java Version: Launcher: 1.8.0_66, Minecraft: 1.8.0_66 Java Path: C:\Program Files\Java\jre1.8.0_66 64 Bit Java: true Launcher Directory: USERSDIR Using Theme: Default Theme by RyanTheAllmighty Showing splash screen and loading everything Checking for updated files! No updates found! Loading external library authlib-1.5.17.jar to classpath Loading external library to classpath Loading external library to classpath Loading external library guava-17.0.jar to classpath Loading external library commons-io-2.4.jar to classpath Loading external library commons-lang3-3.3.2.jar to classpath Checking Minecraft Versions Started Checking account UUID's! Checking For Username Changes Checking For Username Changes Complete Launcher finished loading everything Launcher opening Made By Bob* *(Not Actually) Setting up Bottom Bar Finished Setting up Bottom Bar Setting up Tabs Checking Minecraft Versions Complete Finished Setting up Tabs Showing Launcher Logging into Minecraft! Trying to login with access token! Launching pack Journey to the Core 1.7 for Minecraft 1.7.10 Launching Minecraft with the following arguments (user related stuff has been removed): # There is insufficient memory for the Java Runtime Environment to continue.
I'll paste my log too so any help appreciated. 3) Try resetting Minecraft in Windows Settings > Apps > Apps & Features > Minecraft > Advanced Options > Repair or Reset.
#Atlauncher crashes back to launcher install#
2) Check for and install game Updates in Microsoft Store app > Hub (three dots at top right) > Updates. I keep trying to play to the core and it'll load up and then crash and the launcher pops up again. 1) Run the Store apps troubleshooter at Settings > Update & Security > Troubleshoot.
0 kommentar(er)
