Sorry to be rude like this, but read the f*cking message, I have a 64-bit computer and 64-bit version of Java, I'm well aware of how bad giant modpacks behave on 32-bit...
Now if anyone could tell me if this flaw with the curse client will be fixed in the future that would be lovely.
jtrent238 I have 64-bit, I use the 'edit profile' button to enable the console window (I like seeing it, don't judge), apperently there's a 'known' bug with curseclient that if you edit the profile, minecraft will add a second -xmx one, that is prefilled with half a GB, it only does that on game load, not in the profile itsself, the only solution is reinstalling both cursevoice and the pack, I changed to another laucher for AS2 because of this.
(also for some reason, after a clean install, the 'bug' only happens after you close the minecraft launcher window once)
not trying to boast, but I'm not a noob with java and it's arguments, I know how to allocate more ram (and curse should do that automatically with the slider in the settings) but I've never encountered anything like this, since the second xmx is specified nowhere apart from the logs...
so if it would be possible to allow people to enable the console window (or make it default?) without having that bug, that would make me go back to using the curse client... since not all packs are available on other launchers... and I really like the customizeability of curse client, this bug breaks the experience for me though...
for some reason it specifies the maximum RAM 2 times, that last -XmX is not in my arguments in my minecraft profile, it worked fine before, only started doing this after a restart of the curse client.
The problem persists after reinstalling the curse client.
Anyone know how I can get rid of the second memory setting that I did not set myself, and can't find in any settings file?
0
Sorry to be rude like this, but read the f*cking message, I have a 64-bit computer and 64-bit version of Java, I'm well aware of how bad giant modpacks behave on 32-bit...
Now if anyone could tell me if this flaw with the curse client will be fixed in the future that would be lovely.
0
jtrent238 I have 64-bit, I use the 'edit profile' button to enable the console window (I like seeing it, don't judge), apperently there's a 'known' bug with curseclient that if you edit the profile, minecraft will add a second -xmx one, that is prefilled with half a GB, it only does that on game load, not in the profile itsself, the only solution is reinstalling both cursevoice and the pack, I changed to another laucher for AS2 because of this.
(also for some reason, after a clean install, the 'bug' only happens after you close the minecraft launcher window once)
not trying to boast, but I'm not a noob with java and it's arguments, I know how to allocate more ram (and curse should do that automatically with the slider in the settings) but I've never encountered anything like this, since the second xmx is specified nowhere apart from the logs...
so if it would be possible to allow people to enable the console window (or make it default?) without having that bug, that would make me go back to using the curse client... since not all packs are available on other launchers... and I really like the customizeability of curse client, this bug breaks the experience for me though...
0
error log: http://pastebin.com/F2JU1JPQ
line 85: JVM Flags: 5 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx4096m -Xms256m -XX:PermSize=256m -Xmx512M
for some reason it specifies the maximum RAM 2 times, that last -XmX is not in my arguments in my minecraft profile, it worked fine before, only started doing this after a restart of the curse client.
The problem persists after reinstalling the curse client.
Anyone know how I can get rid of the second memory setting that I did not set myself, and can't find in any settings file?