RAM Problem
- Thread starter Sionyn
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
- Status
Even on the FTB launcher if you have 32bit Java then you be forced to have a maximum of 1GB. I am no expert, but I believe it is a 32bit Java thing. Also just an FYI we do not provide support for the AT Launcher please try the forums that the creator of the launcher provides.
Edit: Again no expert, but that is the maximum memory not allocated memory, if I recall correctly.
Do not get me wrong you can discuss it and if anyone knows the answer they can reply, but as far as official support there is none. I apologize I was merely pointing out that you will get better support for it there.
Last edited:
Read this http://forum.feed-the-beast.com/threads/suggestion-disable-ram-maximum.12831/
It won't help but is a good answer
It won't help but is a good answer
I think the 1GB max for 32bit might be set there because java requires more RAM to run the game, than that which is set aside to the game alone. Usually it seem to use about double of what you set in the launcher. Coupled with that you probably need around 1GB for OS and other bits running, 1GB could be calculated to what's left to work with.
I don't fully understand what's happening in your particular situation, but if you have the launcher set to 1024MB and you're being told you need more RAM, then perhaps you need to do the opposite: turn it downwards. If the launcher's setting is controlling the minimum memory to allocate, and you don't have that much available, then it won't start, even if Minecraft itself may not actually need that much to actually function.
If it's really your machine being limited on RAM that's causing the problem, then you want to make sure you're closing as much stuff as possible before trying to run the game, as well. Web browser, instant messengers, etc. Kill all of it.
Something else you can do is to just start pulling out mods from the pack that you don't think you'll want.
If it's really your machine being limited on RAM that's causing the problem, then you want to make sure you're closing as much stuff as possible before trying to run the game, as well. Web browser, instant messengers, etc. Kill all of it.
Something else you can do is to just start pulling out mods from the pack that you don't think you'll want.
What people need to understand is that the memory allocation you do in the launcher (any launcher, or manually via the -Xms/-Xmx JVM arguments) is not the total amount of memory Java gets to work with. It is only "heap" memory, that is, one of multiple different workspaces the java VM uses. So not only is it not the entire workspace, but it doesn't even include the memory that Java uses to run itself. You're controlling just a small fraction of the overall picture.
And unfortunately, the heap space is completely unrelated to why heavily modded Minecraft crashes with memory errors on 32bit Java VMs. You can set anything you want there, it won't help. It may sound harsh, but you're probably not going to get things stable without a 64bit OS. That's just the shoddy way that Minecraft (and several mods) are implemented.
However, you should check the exact error message that the crashlog is giving you. The specific out of memory error that you can't fix is only one possible out of several, and the others can be fixed. If you're lucky, you'll only get a PermGen error, for example. That one takes all but 30 seconds to fix.
And unfortunately, the heap space is completely unrelated to why heavily modded Minecraft crashes with memory errors on 32bit Java VMs. You can set anything you want there, it won't help. It may sound harsh, but you're probably not going to get things stable without a 64bit OS. That's just the shoddy way that Minecraft (and several mods) are implemented.
However, you should check the exact error message that the crashlog is giving you. The specific out of memory error that you can't fix is only one possible out of several, and the others can be fixed. If you're lucky, you'll only get a PermGen error, for example. That one takes all but 30 seconds to fix.
Just to avoid conflict, the official RR forums are at resonant-rise.com
A good chunk of the members there are members here as well fyi
- Status