trouble with windows build

[Pelicanjoe]

Has anyone else had problems with Windows v9 Java heap being consumed at a rapid pace? I'm clearing the heap about twice a day. I'm running version 1.8.0_91. I used "SageTVSetup_9.0.4.232_RC1.000" to set up Sage. Everything seemed to work fine, now it is eating up Java memory and also giving me "capture device failure while starting data scanning".

Anyone have any suggestions? I've removed defender realtime scanning on sage folders. I've reinstalled java.

Thanks!

Joe

[trallyus]

Originally Posted by Pelicanjoe

Has anyone else had problems with Windows v9 Java heap being consumed at a rapid pace? I'm clearing the heap about twice a day. I'm running version 1.8.0_91. I used "SageTVSetup_9.0.4.232_RC1.000" to set up Sage. Everything seemed to work fine, now it is eating up Java memory and also giving me "capture device failure while starting data scanning".

Anyone have any suggestions? I've removed defender realtime scanning on sage folders. I've reinstalled java.

Thanks!

Joe

What do you have your java heap size set at?

[Pelicanjoe]

Originally Posted by trallyus

What do you have your java heap size set at?

JVMMaxHeapSizeMB - 1024 (Decimal)

[trallyus]

Originally Posted by Pelicanjoe

JVMMaxHeapSizeMB - 1024 (Decimal)

I have mine set to that too but certain programs I have tend to make SageTV not load up if I leave them run at start up I noticed.

I have not had much problems with the new SageTV other then that and my tuners not being as sensitive as they used to be.

I am hoping someone builds a new build of sagetv for windows with any new updates that fixes the problems.

[Fuzzy]

Originally Posted by Pelicanjoe

Has anyone else had problems with Windows v9 Java heap being consumed at a rapid pace? I'm clearing the heap about twice a day. I'm running version 1.8.0_91. I used "SageTVSetup_9.0.4.232_RC1.000" to set up Sage. Everything seemed to work fine, now it is eating up Java memory and also giving me "capture device failure while starting data scanning".

Anyone have any suggestions? I've removed defender realtime scanning on sage folders. I've reinstalled java.

Thanks!

Joe

Are you getting symptoms related to heap usage? Or is it just seeming to build up more usage than you remember v7 using?

[Narflex]

Also, when you say you "are clearing the heap twice a day"...do you mean you're restarting SageTV to do that or just forcing Java to run a garbage collection? There's nothing wrong with it using a lot of the heap unless it is resulting in OutOfMemory errors.

If you want to post your logs from this that'd likely help a bunch (memory statistics are printed in the logs on a regular basis, and then we could also see the capture device error you are getting).

[Pelicanjoe]

Originally Posted by Narflex

Also, when you say you "are clearing the heap twice a day"...do you mean you're restarting SageTV to do that or just forcing Java to run a garbage collection? There's nothing wrong with it using a lot of the heap unless it is resulting in OutOfMemory errors.

I was originally restarting the server, but I read about the trick of pressing delete while in system Information and that seems to work. I am doing it about twice a day. With v7, I never ran up the java heap (other than when I did a new install and forgot to change the registry).

Originally Posted by Narflex

If you want to post your logs from this that'd likely help a bunch (memory statistics are printed in the logs on a regular basis, and then we could also see the capture device error you are getting).

Please see below. I've included the log files.

Thank you!

Joe

[Narflex]

Those heap usage numbers look fine for having multiple clients connected at once. And there wasn't any errors in there relating to data scanning.

[Pelicanjoe]

Originally Posted by Narflex

Those heap usage numbers look fine for having multiple clients connected at once. And there wasn't any errors in there relating to data scanning.

Okay, I never had this Java Heap situation with V7 and my clients are the exact same number as with V7. The attached log does have the Capture Device Failure. It occurred at 11:00am today. I've included just that time in the log.

Thank you for looking into it!

Joe.

[BobPhoenix]

I have found I have better luck (about 4 days so far so not an exhaustive test) with heap memory of 1280 (500 hex) is working better for me than the 1024 (400 hex) I use to use for V7 and Windows.

[Narflex]

Originally Posted by BobPhoenix

I have found I have better luck (about 4 days so far so not an exhaustive test) with heap memory of 1280 (500 hex) is working better for me than the 1024 (400 hex) I use to use for V7 and Windows.

V9 will likely use more memory than V7 due to it also having the Lucene indexes in memory (we tried keeping them on disk, but it just hit too many bugs in Lucene that way).

[Narflex]

Originally Posted by Pelicanjoe

Okay, I never had this Java Heap situation with V7 and my clients are the exact same number as with V7. The attached log does have the Capture Device Failure. It occurred at 11:00am today. I've included just that time in the log.

Thank you for looking into it!

Joe.

Sorry, I'm not sure what exactly is going wrong here...it looks like some of the tuners are working for data scanning...so you should still end up getting EPG data that way; I can't tell why some of them are failing. It would need to be debugged in more detail to determine that.

[sacrament055]

Originally Posted by Narflex

V9 will likely use more memory than V7 due to it also having the Lucene indexes in memory (we tried keeping them on disk, but it just hit too many bugs in Lucene that way).

Narflex, Do you have an opinion about whether or not it's ok to exceed 1024 for JVM heap? I've seen lots of claims that bad things happen above 1024 but I don't believe I've ever seen you post that you should not exceed 1024.

[Fuzzy]

Originally Posted by sacrament055

Narflex, Do you have an opinion about whether or not it's ok to exceed 1024 for JVM heap? I've seen lots of claims that bad things happen above 1024 but I don't believe I've ever seen you post that you should not exceed 1024.

1024 is really the safe limit - this provides a large enough cushion for java to deal with it's rather poor memory management system plus room for garbage collection loads. I've seen people run it up to 1200 or so, and it might work, but it also might lead to problems. At this point, if you have enough extenders/miniclients that the heap is pushing a limit at 1024, you need to switch to a 64-bit server. Currently, that means running the server on Linux.

[Narflex]

Originally Posted by sacrament055

Narflex, Do you have an opinion about whether or not it's ok to exceed 1024 for JVM heap? I've seen lots of claims that bad things happen above 1024 but I don't believe I've ever seen you post that you should not exceed 1024.

SageTV has no problem with larger heap sizes...it's other issues relating to using the 32-bit JVM which really puts the limit on it.