Nicster189 Posted January 4, 2015 Posted January 4, 2015 (edited) Hello, My friend made a modpack which he can run fine. However when I try and run the modpack I get stuck on the mojang screen and in the log the last line it gets stuck on is: [14:28:08] [Client thread/INFO]: Reloading ResourceManager: Default I left the modpack on that line for 30 minutes. The modpack has 4gb of ram dedicated to it which is plenty considering my friend who can run the pack only has 2gb. Here is the full log: http://pastebin.com/Y0q0agE1 I am running java 8 and have the JKD installed (64 bit) my friend also uses java 8. We tried running it on java 7 however had the same problem. We have tried different ram amounts (2,3,4 gb) While the pack is launching only 3gb of ram is being used by the computer. So it's not running out of ram. I have an 8 gb ram computer. Can anyone help me with this? Thanks. Edited January 4, 2015 by Nicster189
Discord Moderator plowmanplow Posted January 4, 2015 Discord Moderator Posted January 4, 2015 Caused by: java.lang.OutOfMemoryError: Java heap space This means you are running out of memory. Please provide a full crash report. On a side note, there are mods in there which should really be updated along with bumping your Forge version up to at least #1240.
Nicster189 Posted January 4, 2015 Author Posted January 4, 2015 The modpack doesn't crash, therefore I can't supply a crash report. I got all of the pastebin text from the log file. I will try updating my forge version however I don't understand why that would be the problem as my friend can run the modpack fine.
Discord Moderator plowmanplow Posted January 4, 2015 Discord Moderator Posted January 4, 2015 The updates are surely secondary. The out of memory error is immediately fatal. That shouldn't happen when you are running 64bit Java on a system with that much RAM. Please provide a link to the pack so that we can debug things.
Discord Moderator plowmanplow Posted January 4, 2015 Discord Moderator Posted January 4, 2015 In the future, please just post the pack link in the original post. Doesn't matter if it's private or whatnot. Sending me a PM with the link means that it won't last for very long since I get so many PMs. The download URL is not direct. Copy.com links need to have "download=1" (without quotes) appended to the URL. Forge should be updated to #1240. You really shouldn't be distributing the texture packs in your modpack archive. More than half of the size of your modpack is texture packs. With Forge #1240, the pack works fine in my test environment (BareBonesPack). I was able to start a SSP world. Double check that you indeed have your memory allocation in the Launcher set to 3G.
Nicster189 Posted January 4, 2015 Author Posted January 4, 2015 We tried all of the suggestions. It's still not working.
Discord Moderator plowmanplow Posted January 4, 2015 Discord Moderator Posted January 4, 2015 Try resetting your pack or incrementing your pack version number. I just added it to my launcher and successfully started a SSP world.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now