Out of memory.

[gabrielcab]

Hello,

I'm getting recently many out of memory errors and SageTV freeze that requires me to restart everything. Currently i have the Java Heap set to 1024, can i use more than that? any downside of using too much Heap memory? My system is:

WHS v1
Intel Core i5
4GB Ram
HD-PVR
4 HD300 extenders

[nyplayer]

You are about the limit Java limitations what you need to do is look at the plugins you are using... maybe remove some.

[gabrielcab]

Reading through google i found that the max java heap size should be no more than 1.8gb, i'll try adding a little more see if there free java heap memory after turning all the extender at once.

[wayner]

In my experience using about 4-5 extenders is all that the system can handle - I do have several plugins loaded and use the Diamond UI. Turning off extenders that are not in use should help. I believe the max for Java in Sage is 1024K, any more than that causes problems, or so I have read.

[tmiranda]

Originally Posted by wayner

In my experience using about 4-5 extenders is all that the system can handle - I do have several plugins loaded and use the Diamond UI. Turning off extenders that are not in use should help. I believe the max for Java in Sage is 1024K, any more than that causes problems, or so I have read.

My experience is also that 4-5 extenders is the max before running out of heap, and I don't use any "heap hungry" plugins.

Heap usage also depends on the number of video, audio, and photos you have. I have thousands of photos, thousands of songs, and hundreds of videos, and that uses a good chunk of heap.

[panteragstk]

Originally Posted by wayner

In my experience using about 4-5 extenders is all that the system can handle - I do have several plugins loaded and use the Diamond UI. Turning off extenders that are not in use should help. I believe the max for Java in Sage is 1024K, any more than that causes problems, or so I have read.

From my experience anything higher than 1024k causes lots of issues.

[gabrielcab]

Originally Posted by tmiranda

My experience is also that 4-5 extenders is the max before running out of heap, and I don't use any "heap hungry" plugins.

Heap usage also depends on the number of video, audio, and photos you have. I have thousands of photos, thousands of songs, and hundreds of videos, and that uses a good chunk of heap.

The plugins I use are:
SageSQJ
Diammond
Commercial Skip
MyMovies
MiniGuide

Is that too much for 4 HD 300 extenders?

[wayner]

I would think that both Diamond and MyMovies use up a lot of Java resources. As long as you don't have all of the extenders on at the same time you should be ok. Sage is supposed to clean up after itself so if you close down unused clients that should help. So should therapeutic reboots every once in a while although I fail to do this myself until something breaks. There is a Java heap monitor plugin that Tom created that is useful.

[panteragstk]

MyMovies is a memory hog for sure. Try disabling it and see what happens.

[pjpjpjpj]

Are you using the auto-convert function of Sage on (m)any of your recordings? I started using it recently and I am seeing ever-growing memory usage in the SageTVService.exe process (in Windows Task Manager). There was indication somewhere in another thread that there might be a memory leak associated with the auto-convert.

Being lazy/busy, I haven't bothered to look into it further or file a bug report, I just stop/restart the service every couple of days manually.

[heffneil]

My memory usage has been growing out of control. I enable the web interface to control my extenders. After reading this here I realized that it leaves them on which is probably causing me issues!

Neil

[Griff]

I have Sage configured to run as a service. I think I also inadvertently set it up (when I reinstalled on a Win7 computer) to load minimized at Windows startup.
Is there any reason to have both the sage service and Sage running minimized on the server? I use Sage through extenders, and don't watch Sage on the server, and only occasionally need to open Sage on the server to configure things (sometimes logging in remotely through Splashtop).

When Sage is running on the Server, in addition to running as a service, I see the Sage process run up to almost half a gig. If I close Sage on the server, the service continues to run, programs record, and I can use all my extenders, without the huge memory hit of running Sage minimized in the backgrounds.

[nyplayer]

No need to run the both just run the Service.