Changing JVM Heap Size on Windows 10 64bit

[Lucas]

Hi all,

after running SageTV for 12years on a WinXP server I finally migrated it to Windows 10 64bit on the same hardware.

Everything works extremely well with the exception of my FireDTV firewire tuner which is not seen by SageTV.

The other issue I noted was that when trying to change the JVM Heap Size from the default 400mb to something larger, the registry change is not taking effect. SageTV still has a 400mb Heap Size.

On Win 10 64 bit, the registry parameter is stored in
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV"

The "WOW6432Node" hasn't been documented anywhere in here.

It's been 6 years since my last SageTV reinstall on the then new PC hardware and I don't remeber anything else that needed to be changed for effecting a change to the Heap Size.

Any ideas?

[nyplayer]

Originally Posted by Lucas

Hi all,

after running SageTV for 12years on a WinXP server I finally migrated it to Windows 10 64bit on the same hardware.

Everything works extremely well with the exception of my FireDTV firewire tuner which is not seen by SageTV.

The other issue I noted was that when trying to change the JVM Heap Size from the default 400mb to something larger, the registry change is not taking effect. SageTV still has a 400mb Heap Size.

On Win 10 64 bit, the registry parameter is stored in
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV"

The "WOW6432Node" hasn't been documented anywhere in here.

It's been 6 years since my last SageTV reinstall on the then new PC hardware and I don't remeber anything else that needed to be changed for effecting a change to the Heap Size.

Any ideas?

just do a regedit and do a find on JVMMaxHeapSizeMB do a find next until you get to the bottom .... easiest way without having to do anything special..

[BobPhoenix]

It is my understanding that you need 32 bit OS for Firewire tuners to work.

[Lucas]

Originally Posted by nyplayer

just do a regedit and do a find on JVMMaxHeapSizeMB do a find next until you get to the bottom .... easiest way without having to do anything special..

Thanks! Why didn't I think of that!

Found it. There was another SageTV branch under the VirtualStore.....

[wayner]

Making the JVM size higher than 400h or 1024(base 10) won't help since Sage uses 32 bit Java. Hopefully someone will fix that soon in V9 - you may experience issues when using all three of your extenders at once.

[tcarlus]

Pretty sure Wayners answer was meant for the 32bit SageTV. This thread is about the latest 64 bit version.
If there is going to remain a 32 bit installer, I'd recommend it stay ASIS but the registry entry for 64bit be more than 1GB... say 800h. Otherwise, You just need the 32 bit version anyway. Lack of memory is what drove me to 64bit. Keep up the good work on 64bit !

[BobPhoenix]

Originally Posted by tcarlus

Pretty sure Wayners answer was meant for the 32bit SageTV. This thread is about the latest 64 bit version.
If there is going to remain a 32 bit installer, I'd recommend it stay ASIS but the registry entry for 64bit be more than 1GB... say 800h. Otherwise, You just need the 32 bit version anyway. Lack of memory is what drove me to 64bit. Keep up the good work on 64bit !

Actually based on the post date the 64 bit version of SageTV didn't exist when they were made.

[wnjj]

On this subject, I realized one thing I should have added is to increase the default heap for 64-bit. Will try to get that done before the final installers are released.