7.021.244 Does not release heap usage well

[Email68]

Been really keeping track of the heap size as that has been a real issue for my sage use.

I removed all the plugins except commercial skip and TWit. This helped lower my overall JVM Heap use but I have been watching to see if it lowers itself after a period of no being used.

I had two extenders on one watching a DVD and another a TV recording. The help climbed to around 400MB.

Now that everything has been off for a couple of hours, I turned on one extender and went right to the system information to check and the heap is already at 350MB. Which is about twice as high as when one extender is turned right after a sage server restart.

I think over time this may continue to creep. No reason it should be using 350MB with nothing playing, no recording, and only one extender viewing the info page.

It would be nice to have a detailed information about this JVM heap and what its all about.

-Tim

[Fuzzy]

JVM heap's never shrink. That's just how Java is designed. When memory is requested, the heap is expanded as much as it needs (up to the predetermined max). However, when the program releases that chunk of memory - it is never shrunk down and returned to the OS.

[tmiranda]

If you go to the System Information screen and press "Delete" it will run the garbage collector and free up heap space.

[Email68]

What happens when it just keeps rising then and maxes out? You just slow down and/or lock up?

[tmiranda]

Originally Posted by Email68

What happens when it just keeps rising then and maxes out? You just slow down and/or lock up?

It will get slower and slower and then eventually crash. If that happens you have a memory leak somewhere.

Remove ALL plugins and see if the heap keeps growing. I doubt it, but if it does you need to file a bug report with Sage. Then try adding plugins one at a time until you find the problem.

I see you are down to two plugins. I have not had issues nor have others reported issues with CommercialDetector, but that does not mean it's not the problem.

[timg11]

I'm seeing a similar problem. Sage reports the HD-PVR stopped working at 15:11, and after that nothing else is recorded for the rest of the day. I find SageTV in the tray and completely unresponsive to left or right clicks at 22:00. The tooltip says "SageTV 2" instead of the usual "SageTV.

I track SageTV usage hourly with a script that Greps the output of tasklist.exe. Here are the results for today:

"2010-10-27 06:00:00","SageTV.exe                    3888 Console                    1    245,912 K"
"2010-10-27 07:00:00","SageTV.exe                    3888 Console                    1    251,480 K"
"2010-10-27 14:58:15","SageTV.exe                    3888 Console                    1    273,112 K"
"2010-10-27 15:00:00","SageTV.exe                    3888 Console                    1    459,804 K"
"2010-10-27 16:00:00","SageTV.exe                    3888 Console                    1    453,732 K"
"2010-10-27 18:00:00","SageTV.exe                    3888 Console                    1    458,604 K"
"2010-10-27 20:00:00","SageTV.exe                    3888 Console                    1    456,348 K"
"2010-10-27 21:00:00","SageTV.exe                    3888 Console                    1    457,676 K"
"2010-10-27 22:06:23","SageTV Restarted "

The gaps are because the computer is in standby. Right when a HD-PVR recording starts at 15:00, the memory doubles.

In the sagetv.log, I find this around the point where I re-started it at 22:00:

Wed 10/27 22:01:15.418 [FinalRender-SAGETV_PROCESS_LOCAL_UI@18d6fb7] ImageUtils creating scaled masked copy width=83 height=83 option=null BufferedImage@11476c4: type = 2 DirectColorModel: rmask=ff0000 gmask=ff00 bmask=ff amask=ff000000 IntegerInterleavedRaster: width = 121 height = 121 #Bands = 4 xOff = 0 yOff = 0 dataOffset[0] 0
Wed 10/27 22:01:15.968 [AWTThreadWatcher-SAGETV_PROCESS_LOCAL_UI@e816f5] EventThread-SAGETV_PROCESS_LOCAL_UI Hang Detected - hang time = 2252
Wed 10/27 22:01:16.566 [AWT-EventQueue-0@1729854] Removed system shell hook
Wed 10/27 22:01:16.567 [AWT-EventQueue-0@1729854] VF processing on UI Thread VFJob[Sleep r=0.0 t=0 file=null ifn=null]
Wed 10/27 22:01:16.568 [AWT-EventQueue-0@1729854] Seeker.finishWatch(UIManager:localhost@@SAGETV_PROCESS_LOCAL_UI-a0dcd9)
Wed 10/27 22:01:16.719 [AWTThreadWatcher-SAGETV_PROCESS_LOCAL_UI@e816f5] EventThread-SAGETV_PROCESS_LOCAL_UI Hang Detected - hang time = 3003
Wed 10/27 22:01:17.470 [AWTThreadWatcher-SAGETV_PROCESS_LOCAL_UI@e816f5] EventThread-SAGETV_PROCESS_LOCAL_UI Hang Detected - hang time = 3754
Wed 10/27 22:01:18.221 [AWTThreadWatcher-SAGETV_PROCESS_LOCAL_UI@e816f5] EventThread-SAGETV_PROCESS_LOCAL_UI Hang Detected - hang time = 4505
Wed 10/27 22:01:18.972 [AWTThreadWatcher-SAGETV_PROCESS_LOCAL_UI@e816f5] EventThread-SAGETV_PROCESS_LOCAL_UI Hang Detected - hang time = 5256
Wed 10/27 22:01:19.723 [AWTThreadWatcher-SAGETV_PROCESS_LOCAL_UI@e816f5] EventThread-SAGETV_PROCESS_LOCAL_UI Hang Detected - hang time = 6007
Wed 10/27 22:01:20.474 [AWTThreadWatcher-SAGETV_PROCESS_LOCAL_UI@e816f5] EventThread-SAGETV_PROCESS_LOCAL_UI Hang Detected - hang time = 6758
Wed 10/27 22:01:21.225 [AWTThreadWatcher-SAGETV_PROCESS_LOCAL_UI@e816f5] EventThread-SAGETV_PROCESS_LOCAL_UI Hang Detected - hang time = 7509

This type of hang has occurred several times since I installed .21

[Email68]

Ya, this is crazy.

Only one extender on, and one show recording. Heap use was at 706 or something close, I hit the delete key while viewing it and it dropped to 160.

This can't be right.

I would hope sage monitors the beta forum, it would be ridiculous to have to put in a ticket for everything.

[paulbeers]

Originally Posted by Email68

Ya, this is crazy.

Only one extender on, and one show recording. Heap use was at 706 or something close, I hit the delete key while viewing it and it dropped to 160.

This can't be right.

I would hope sage monitors the beta forum, it would be ridiculous to have to put in a ticket for everything.

Isn't filing a bug report, kind of the point of a Beta/RC?

[Email68]

Originally Posted by paulbeers

Isn't filing a bug report, kind of the point of a Beta/RC?

Same as the point of a beta forum...

[Fuzzy]

Originally Posted by Email68

Same as the point of a beta forum...

not really. This is a User-to-user forum. It is here so they can relay information to the user base, and so we can help each other with configuration/hardware issues and other similar assistance. The bug reporting system is the primary method of notifying the developers of a discovered problem, and is really the only way it can be expected to be observed, tracked and fixed.