java heap size in system status reporting incorrectly?

[Mr. Smartyman]

I think I must be missing something. In system status my java heap is showing 146/225/779 (used/total/max). If I have my heap size set to 1024, shouldn't that last number be 1024? I double checked the registry entry and it still shows 1024.

[Fuzzy]

Sounds like you aren't looking at the right part of the registry. 779 (or about) is what will show if sage doesn't find a JVMMaxHeapSizeMB entry. Search the registry for JVMMaxHeapSizeMB, and see if it shows up anywhere else.

[Mr. Smartyman]

thanks for the reply. I found two places in the registry yesterday and they were both set to 1024, but I had only searched for JVM. Searching for the whole key today I found four:

HKEY_USERS\S-1-5-21-2505956771-2493310666-272390289-1000\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV

HKEY_USERS\S-1-5-21-2505956771-2493310666-272390289-1000_Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV

HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV


I'm not sure why there are four, but they are all set to 1024.

[jusjoken]

What OS version and how did you install V9?

k

[Mr. Smartyman]

windows 7 and I used the installer. I was considering an uninstall/reinstall to see if that would clean things up.

[Fuzzy]

Best thing to do would be to delete all those keys, and rerun sage - it should recreate the key on first run, and you can find the single entry.

[jusjoken]

Typically if it is not creating the key on first run then there is a registry permission issue. Do as Fuzzy suggests but if that does not resolve it then you either need to add "everyone" to permission at the Frey level and let it replicate those permissions down, or simply delete the Frey level and run the installer and select repair.

k

[Mr. Smartyman]

well, for completely unrelated reasons, I had to reinstall my operating system.

This time the installer kept throwing errors at me when I tried to install Sage, so I just moved the necessary files. Edited the registry and I'm up and running with 1024MB heap.

Thanks for all the help.

[Fuzzy]

Originally Posted by Mr. Smartyman

well, for completely unrelated reasons, I had to reinstall my operating system.

This time the installer kept throwing errors at me when I tried to install Sage, so I just moved the necessary files. Edited the registry and I'm up and running with 1024MB heap.

Thanks for all the help.

What errors are you seeing? I've done quite a few sage installs with the current installed, and haven't seen any.

[Mr. Smartyman]

a lot of .dll errors. I ran the installer over my previous install and it worked great. This time trying to install V9 over a new install of V7 it just didn't work. Not sure why, but i just copied the .jar file over and all was good.

I ran the installer over my client install (when I first upgraded to V9) and that worked fine.

I suspect it was something to do with re-installing my system, win 7. Maybe I should have done all the system updates first? I know I did some, but you know how it will say you've got 10 updates, and then those lead to more updates when you restart.

[Fuzzy]

You shouldn't need to install v7 at all. On a clean windows install, just install v9 directly. The only reason I can see to install v7 first, is if you intend to use the SageTV Decoders (which are not included in v9 due to licensing reasons).

[Mr. Smartyman]

I guess I thought that if you had a license and wanted to use EPG data, you had to install 7 first. Either way, it's working now. Thanks for the help.