Startup error still present in 2.5.2.1

[orgon3]

I just installed 2.5.2.1 and noticed the auto-limit was set to 1152. I installed and upon running the program, the same startup error occurred (could not create java virtual blah blah blah). I just did a little brute test and the highest value that works for me (personally) is 1110. 1111 and beyond result in that startup error.

I have 8GBs of RAM installed. I'm running Windows 7 64-bit. I am not forcing UMS to use Java64.

[Madoka]

Ok, that's interesting. As I also have 8 GB of RAM, am on Win7 64-bit, but I only have 64-bit Java installed.

2.5.2 starts and works ok for me, but UMS reports:

03-19 12:56:00 Memory: 1137 MB

with the default 1280 MB at installation. In fact, UMS has always reported a little less memory than the default value UMS uses (which I never change). Still, it works so I leave it.

[SubJunk]

I just quietly released 2.5.2.2 which reverts the memory change so that should work now

[orgon3]

I just quietly released 2.5.2.2 which reverts the memory change so that should work now

You sneak, you.

[orgon3]

Ok, that's interesting. As I also have 8 GB of RAM, am on Win7 64-bit, but I only have 64-bit Java installed.

2.5.2 starts and works ok for me, but UMS reports:

03-19 12:56:00 Memory: 1137 MB

with the default 1280 MB at installation. In fact, UMS has always reported a little less memory than the default value UMS uses (which I never change). Still, it works so I leave it.

Yeah, I still use 32-bit browsers since the 64bit ones still suck.

[ExSport]

You can use 32bit browsers (with 32bit Java) but also install 64bit Java for UMS. It is nothing against anything. UMS will benefit from 64bit Java that you can allocate more memory for UMS.

[orgon3]

You can use 32bit browsers (with 32bit Java) but also install 64bit Java for UMS. It is nothing against anything. UMS will benefit from 64bit Java that you can allocate more memory for UMS.

I was referring to the fact that he said he only had 64-bit Java installed. Can the installer simply look for Java 64-bit, and if it's available, force UMS to use it? (aka: I'm lazy)

[Madoka]

UMS will benefit from 64bit Java that you can allocate more memory for UMS.

Is this my 2.5.2 works for while while it doesn't for others, or is it a completely different reason altogether?

[Optimus_prime]

From looking at the code, the installer doesn't look for 64bit java first but if you have 32bit installed first. Then it checks to see if 64bit. Thats how i read it anyway, i could be very wrong however

Is this my 2.5.2 works for while while it doesn't for others, or is it a completely different reason altogether?

Well it has to do with how much of the java heap size is being used by other programs and how much ram java allocates to the heap in the first place. You will find it will change every time

[orgon3]

From looking at the code, the installer doesn't look for 64bit java first but if you have 32bit installed first. Then it checks to see if 64bit. Thats how i read it anyway, i could be very wrong however

For me, UMS has always used 32bit Java, unless I specifically tell it not to. 64bit Java has always been available, but it's never been used by default. Kind of defeats the point of having it.