Java Heap question

[Evil_Attorney]

Originally Posted by willieb

Ok, I was able to increase my heap size and it seems to have stuck. I used the SageTV Registry Settings program that I downloaded from babgvant's web site. You can google it. I set mine at 1280. Right now I am showing max of 1297. I'll let you know if somehow it reverts.

Do you know what registry entry was changed?

[jusjoken]

I created a clean Win 10 test system and performed various install tests and in every case I am able to just search the register for "JVMMaxHeapSizeMB" and change the value to 400 and SageTV does not overwrite this value.... it stays at 400 and the Heap is at 1038 in the System Information screen.

So obviously something else is blocking this so we need to collect some info from those having this issue.... like OS, x86 vs x64, upgrade over v7 or clean install, upgrade over a previously manually upgraded system etc.

k

[wnjj]

jusjoken,

Can you maybe build them a launcher.exe with some debug logging in it? That may help to see if it fails to access the key or find the value. Both cause the default of 768.

[jusjoken]

Originally Posted by wnjj

jusjoken,

Can you maybe build them a launcher.exe with some debug logging in it? That may help to see if it fails to access the key or find the value. Both cause the default of 768.

It's a great suggestion, just not sure high on my long list of things I am working on. If we don't figure this out before I get some time then perhaps I could dig into the code and add some debugging in the launcher to see what is happening in this area.

k

[jgsouthard]

I just completed a v7 to v9 upgrade, and my Java Heap setting also got changed to 779 instead of the 1024 I had previously set in v7.

When I went into Regedit and searched for all instances of JVMMaxHeapSizeMB, I found several (at least three or four). All but ONE of them still had the desired hex 400 / decimal 1024 setting, but that last one that had a setting of 0. I changed it to 1024, restarted SageTV, and all was well.

I think the OP claimed that he only found one instance of JVMMaxHeapSizeMB in the registry. While I won't dispute that, I'll note that a common issue with searching the registry is accidentally starting somewhere within the registry rather than at the top (searches are top to bottom). Regedit opens to where ever you were the last time you were in the registry, so unless you take the deliberate step of moving the cursor to the top of the registry before starting the search, the search may be incomplete. My hunch is that there is still a 0 setting in there somewhere.

[jusjoken]

Originally Posted by jgsouthard

I just completed a v7 to v9 upgrade, and my Java Heap setting also got changed to 779 instead of the 1024 I had previously set in v7.

When I went into Regedit and searched for all instances of JVMMaxHeapSizeMB, I found several (at least three or four). All but ONE of them still had the desired hex 400 / decimal 1024 setting, but that last one that had a setting of 0. I changed it to 1024, restarted SageTV, and all was well.

If you don't mind i would like to see the results of the search to understand the different locations you found this key so i can see if the installer might need tweaking a bit if its creating something in the wrong location.

thanks for posting your positive experience.

k

[jgsouthard]

Originally Posted by jusjoken

If you don't mind i would like to see the results of the search to understand the different locations you found this key so i can see if the installer might need tweaking a bit if its creating something in the wrong location.

thanks for posting your positive experience.

k

I found JVMMaxHeapSizeMB entries in the following registry keys:

HKEY_CLASSES_ROOT\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV
HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV
HKEY_USERS\S-1-5-21-1920200382-3535082570-624732948-1000\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV
HKEY_USERS\S-1-5-21-1920200382-3535082570-624732948-1000_Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV

Unfortunately, I didn't notice WHICH of these was the one that got reset to 0 when I ran the v9 Installer. I believe that it MAY have been the first HKEY_USERS entry, since I vaguely remember finding three entries correctly set to 1024, then one set at 0 (which I changed to 1024), then another one set to 1024.

[jusjoken]

Originally Posted by jgsouthard

I found JVMMaxHeapSizeMB entries in the following registry keys:

HKEY_CLASSES_ROOT\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV
HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV
HKEY_USERS\S-1-5-21-1920200382-3535082570-624732948-1000\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV
HKEY_USERS\S-1-5-21-1920200382-3535082570-624732948-1000_Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV

Unfortunately, I didn't notice WHICH of these was the one that got reset to 0 when I ran the v9 Installer. I believe that it MAY have been the first HKEY_USERS entry, since I vaguely remember finding three entries correctly set to 1024, then one set at 0 (which I changed to 1024), then another one set to 1024.

By chance was your Win 10 an upgrade from Win 7 or another previous version ? Wondering if the win 10 upgrade process duplicates some entries.

k

[Fuzzy]

Originally Posted by jusjoken

It's a great suggestion, just not sure high on my long list of things I am working on. If we don't figure this out before I get some time then perhaps I could dig into the code and add some debugging in the launcher to see what is happening in this area.

k

Alternatively, i don't really see harm at this stage changing the default to 400h in the launcher, to simply avoid this issue going forward.

[jgsouthard]

Originally Posted by jusjoken

By chance was your Win 10 an upgrade from Win 7 or another previous version ? Wondering if the win 10 upgrade process duplicates some entries.

k

Yes, it was an in-place upgrade from Win 7 to Win 10, during the free upgrade period. And yes, I suspected that duplicate entries might have resulted from that. I've seen that happen with multiple versions of the application itself as well, although in this case I did a clean install of SageTV v7 on Windows 7 a couple of years prior to the Windows 10 upgrade.

[SDeGonge]

I found a Frey Technologies key in 3 or 4 places but the only key that had a SageTV and JVMMaxHeapSizeMB entry was here...

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV\JVMMaxHeapSizeMB

Do you think I need to manually add this information to the other locations to get Sage to accept the setting?

[jusjoken]

Originally Posted by SDeGonge

I found a Frey Technologies key in 3 or 4 places but the only key that had a SageTV and JVMMaxHeapSizeMB entry was here...

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV\JVMMaxHeapSizeMB

Do you think I need to manually add this information to the other locations to get Sage to accept the setting?

it wont hurt to try.

k

[jgsouthard]

Originally Posted by SDeGonge

I found a Frey Technologies key in 3 or 4 places but the only key that had a SageTV and JVMMaxHeapSizeMB entry was here...

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV\JVMMaxHeapSizeMB

Do you think I need to manually add this information to the other locations to get Sage to accept the setting?

As jusjoken indicated, I think it's worth a try. But for extra caution, Export each key before you add anything. Then if it doesn't work, you can double-click each *.reg file to re-import the original key and put it back the way it was.

The thing that's odd is that having those keys missing would seem to indicate that a maximum Java Heap Size was never set on your installation (so the defaults are getting used), vs. having it previously set to 1024. But I don't know how SageTV works in that regard, so I could be wrong. I think once upon a time I may have used some SageTV utility or plug-in to set the Java Heap Size (vs. manually editing the registry), and it may have added some keys that aren't part of the normal installation.

[Evil_Attorney]

I just re-searched my registry and confirmed only one JVMMaxHeapSizeMB entry at: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV\

Again, if I delete this entry, Sage adds it back with a 0 value, so it seems to be looking at this value at startup, but just doesn't implement the 400 value for me. Perhaps a plugin could be messing with this? I am using the latest beta for Phoenix and the web interface. Other stats are that upgraded from v7, am running Win 10 64, and have 32-bit Java 1.8.0_111. Noticed there was a Java update available to version 1.8.0_121, but updating didn't help either.

[Fuzzy]

The heap is set up long before any plugins are close to looked at, so I can't imagine that has anything to do with it.

[tvmaster2]

Originally Posted by willieb

Hmmmmm. I'm at 779 too and I know I went up to 1024 years ago. That might explain the increased frequency of the spinning circle I have seen with version 9. Will have to see if I can increase on Saturday. I will let you know if it "takes" for me. If you figure it out please post the solution. Thanks.

I wonder if this will explain my live video just stopping for no reason

[UgaData]

Babgvant (Andy vt,s Tool & Blog) has a Sage registry application. One of the things it will set is the Java heap.

http://babgvant.com/files/10/default.aspx

It is meant for SageTV v7 but i have recently used against v9 and all seems OK (it did change the Java heap size)

[sacrament055]

I was seeing a similar issue yesterday after having upgraded my client to the latest version and it turned out the Sage Client app didn't have proper permission to the REG keys so it was ignoring my change to max out the memory at 400h and my disabling of the sagetv demux.

I tried opening it as administrator and noticed it worked correctly then I changed reg permissions to give "everyone" full control and it works fine now without needing to open as administrator.

[Fuzzy]

I think this is something the installer WAS setting when creating those keys initially, but on upgrades, it might not be touching the permissions.

[jusjoken]

Originally Posted by sacrament055

I was seeing a similar issue yesterday after having upgraded my client to the latest version and it turned out the Sage Client app didn't have proper permission to the REG keys so it was ignoring my change to max out the memory at 400h and my disabling of the sagetv demux.

I tried opening it as administrator and noticed it worked correctly then I changed reg permissions to give "everyone" full control and it works fine now without needing to open as administrator.

What were you upgrading from/to?

k