Out of Memory: Java Mem up to 768MB!

[skyeclad]

Over the last 2 weeks, I've been getting out of memory errors. Sage thinks that I have a bad plugin, which is probably true. Since I didn't add anything, one of the updates must have caused this. Unfortunately, I don't recall what has recently updated. Any way to easily diagnose what plugin would gobble up all memory?

[panteragstk]

Disable them all, then add them back one at a time.

[shatter]

I kept adjusting the java mem to like 1024MB and finally upped the memory on my HTPC to 12GB from 4GB and haven't had the problem occur again. Might have just been a dumb coincidence though.

[FMAX]

I keep getting freezes and Playback problems.

I have 2 HD100, 1 HD200 and an MVP. The MVP is usually off. I have 2GB in my server, had 4GB but did same thing. JVM max size is 1038, I cant go any higher. It must be a plug in, don't know which. I trimmed down my comskip and Commercial detection settings to what I can live with. I use Standard Theme, however I used for Ortus Trailers for awhile, uninstalled but still problems. Is it Ortus Fanart? I have Enable automatic metadata true, but all others false and limit as 4. Are there more optimized settings. I can't pinpoint where the hog is. When every thing stops I have to shutdown sage service and restart. 1038/1038/1038 aint good is it??

Any pointers would help, I like the fanart and comskip is a must.

Running Core 2 Duo 2.8ghz FSB 1066, typically 55 processes,5-15%, 50% with comskip, 1745 of 3808 including virtual memory, 2GB Physical 400mHz
SATA II & III drives all Black edition WD. Windows XP 5.1, Sage TV 1.9.256, Java 1.6.0_26, STV V7-7.1.9.5-2011081001

[Slugger]

The common response to this issue is to disable all your plugins and then enable one of them and run it for a few hours/days/whatever and when you're convinced that's not the one causing the problems, enable a second one, run it for a day or whatever, repeat until you find the offending plugin. When you find it, disable all but the offender and ensure it causes the same issues when it's the only one running. If so, great then that's the problem plugin. If not then you need to find the combination of plugins that causes the problems and determine if there's an issue with that set of plugins interacting with each other. Not fun, but that's really the standard course of action when trying to troubleshoot plugin issues.

[gplasky]

With only 2 GB of RAM I doubt (I could be wrong) that you have 1038 of contiguous memory space for your java heap. It must be contiguous memory for java to use it. I would back it down to 768 or 864 and try running it there for a time. (I only have 2GB and the best I can do is 864.)

Gerry

[FMAX]

Ill try 864, but I had 4GB (3.5 usable) and still had same issues.
Nothing else runs on my server except virus protection.

I read someone had their heap at 13** and 12**.

I'm guessing I could only do that under 64 bit.