NodeCraft
Fixing memory issues
One of the most common issues encountered when installing Pixelmon is the user's system running out of memory (RAM). Pixelmon has many large assets, such as models, textures, and music, that require significantly more memory to load compared to vanilla Minecraft and most other mods, and not having enough memory will cause Minecraft to either crash or freeze while loading.
Identifying the error
Memory errors are not the only cause of Minecraft not loading. Before attempting to fix a memory error, it must first be confirmed that a memory error is causing the problem.
Crashing
If Minecraft crashes when attempting to start up, it is possible that the crash is caused by running out of memory. To check whether this is the case, you will need to look at the crash report that is displayed after Minecraft crashes. The first line of the crash report after "Description" is the start of the actual crash. Look for any of the following lines.
- "java.lang.OutOfMemoryError: Java heap space"
- "net.minecraftforge.fml.common.LoaderException: java.lang.OutOfMemoryError: Java heap space"
- "net.minecraftforge.fml.common.LoaderException: java.lang.NoClassDefFoundError: com/pixelmonmod/pixelmon/..."
- "SplashProgress has detected a error loading Minecraft."
- "Caused by: java.lang.IllegalAccessError: tried to access field net.minecraft.client.renderer.entity.RenderManager.field_178636_l from class com.pixelmonmod.pixelmon.client.ClientProxy"
If the crash begins with any of these lines, then Minecraft is crashing because it ran out of memory.
Freezing
If Minecraft freezes on the loading screen, it is very likely that Minecraft has run out of memory. In particular, if the Forge loading screen is enabled and stops progressing when loading models ("ModelManager 9/22"), Minecraft definitely ran out of memory.
Fixing the error
To fix an issue with running out of memory, more memory must be allocated to Minecraft (at least 2G).
