so as the Launcher suggested to me yesterday, i downloaded the Launcher msi which should speed up my MC.
since then, i could no longer launch MC with my java arguments:
-Xmx1536M -Xms1536M -XX:ParallelGCThreads=2
these worked fine before updating the launcher to 1.6.11
I am using winXP 32bit and i'm refusing to BUY a new OS that to infantilizes the user, even when logged in as admin.
If you could help me get the latest Launcher that used the Javaversion the user installed (Java7), i'd be very glad.
as an alternative, you could make the Launcher check, which java is the latest supported by the user's OS and download this instead.
i am confused now...
the installed java is jre7.72 build 1.7.0 -> when telling the launcher to use this one, the arguments do not work
the java used by MC if not telling to use any specific version is build 1.8.0 and even the archive at java.com isn't helping in finding out if that would be java7 or 8
but with 1.8.0 my arguments work and the game starts.
then again when using java build 1.8.0, the "mcpatcher1.8.1" version of MC has texture and sound bugs.
Your JVM arguments are marginal for a 32bit OS. It is certainly possible that after any change to the JVM version (even minor bugfix updates) that 1536 became too large for the JVM to start successfully.
On a 32 bit OS the whole process size is limited to 2G of memory. Your parameters assign most of that limit to the heap, leaving less than 512M for the JVM memory, the Java code, the JVM stack, video driver native memory allocations, etc.
Your MC will probably work if you reduce your memory allocation back to the defaults.
My OS recognizes 3GB of the 4GB that are built into the machine, the OS with background tasks needs less than 1 GB and most times even less than half a GB.
so as allocating 1536M worked fine before, i don't get why it suddenly should not anymore.
allocating less would result in half of the ressources being unused and a lagging game that is likely to crash by being "out of memory".
so how can i get back to MC using the Java version i want, where it last worked?
Don't care how much memory your OS sees. No singleprocess can see more than 2G of it on a 32bit OS.
Any change to your minecraft setup can change how much non heap memory is required.
Mojang ships 200M more code, then that's 200M less heap you can fit into 2G.
Oracle ships 200M more code, then that's 200M less heap you can fit into 2G.
changing allocated RAM to 1408M fixed the problem, although nothing else had changed that possibly could've changed the required RAM for the JVM, except for the new Launcher.
I want to apologize if i were rude in my request, but can someone provide the previous launcher.jar?
since then, i could no longer launch MC with my java arguments:
-Xmx1536M -Xms1536M -XX:ParallelGCThreads=2
these worked fine before updating the launcher to 1.6.11
I am using winXP 32bit and i'm refusing to BUY a new OS that to infantilizes the user, even when logged in as admin.
If you could help me get the latest Launcher that used the Javaversion the user installed (Java7), i'd be very glad.
as an alternative, you could make the Launcher check, which java is the latest supported by the user's OS and download this instead.
i am confused now...
the installed java is jre7.72 build 1.7.0 -> when telling the launcher to use this one, the arguments do not work
the java used by MC if not telling to use any specific version is build 1.8.0 and even the archive at java.com isn't helping in finding out if that would be java7 or 8
but with 1.8.0 my arguments work and the game starts.
then again when using java build 1.8.0, the "mcpatcher1.8.1" version of MC has texture and sound bugs.
On a 32 bit OS the whole process size is limited to 2G of memory. Your parameters assign most of that limit to the heap, leaving less than 512M for the JVM memory, the Java code, the JVM stack, video driver native memory allocations, etc.
Your MC will probably work if you reduce your memory allocation back to the defaults.
so as allocating 1536M worked fine before, i don't get why it suddenly should not anymore.
allocating less would result in half of the ressources being unused and a lagging game that is likely to crash by being "out of memory".
so how can i get back to MC using the Java version i want, where it last worked?
Any change to your minecraft setup can change how much non heap memory is required.
Mojang ships 200M more code, then that's 200M less heap you can fit into 2G.
Oracle ships 200M more code, then that's 200M less heap you can fit into 2G.
I want to apologize if i were rude in my request, but can someone provide the previous launcher.jar?
that could fix it so that i can use 1536M again.