7.1.7 Randomly Closing - Java / Memory Problem?

[bmh]

Ever since I installed 7.1.7, I've been having issues with SageTV just randomly closing. I thought it may be due to the Java heap size so I changed it to 1024mb but that didn't seem to help. Last night after watching a recorded show, I hit exit on my remote and it crashed. There's no warning or message, SageTV justs closes. The one thing I've noticed is that power cycling the extenders seems to quickly max the Java heap and speed up the frequency of the crashes. Anyone else having this issue?

[carlgar]

On Sunday morning I did encounter Java heap issues with version 7.1.7. Sage did not crash on me but my system did go to sleep. Sage did generate a system message of "out of memory", the body of the message did suggest increasing the Java heap size which I did as soon as I could. I have not seen any further issues. I have Java version 1.6.0_24 and am running on a 64 bit windows 7. Perhaps your crash occurred while trying to write the system message. Have you increased the heap size? I believe the extenders use the same heap space as the server so the extenders appears to max it out. But Sage probably should be giving warning messages that heap space is low so it be corrected before crashes are caused.

[bmh]

Thanks for your input, Carlgar . Yes, I do have my heap set at 1024mb (400d). After it crashed last night, I went ahead and updated Java to version 24. We'll see if that helps. I forgot to mention that this is happening on a fresh install of both Windows 7 64 bit and Sage 7.1.7.

[Opus4]

bmh: You've got posts in the customizations sections of the forum. Do you still have active customizations? If so, you should first try disabling or uninstalling them all to see if the issue remains.

- Andy

[bmh]

The plugins I have installed are Diamond 3.30, Comskip Playback, and SJQ4. I haven't heard of anyone having issues with the latest Diamond and Comskip plugins. Also, I just installed SJQ4 a few days ago so I wouldn't think that would be the culprit either. Do you think it will help to turn on logging in Sage? I'd really hate to disable the plugins as the WAF will plummet

[panteragstk]

Unless they fixed the memory leak issue in diamond that could be your problem. I use it and have had it happen, but it hasn't lately (in a long time actually).

[bmh]

Originally Posted by panteragstk

Unless they fixed the memory leak issue in diamond that could be your problem. I use it and have had it happen, but it hasn't lately (in a long time actually).

I believe it was fixed with the latest version. Before Diamond 3.30, I tried SageMC with 7.1.7 and had the same problem. I have since reinstalled Windows 7 and SageTV.

[FlyingDoc]

As of yesterday I am working a similar bug with Sage ... client crashes to desktop with no warning frequently ... most often happens when starting playback or skipping trough a video during playback. This is 7.1.7 with a colossus installed but the issue doesnt seem to be related to recording via colossus or my other tuners. I have seen it immediately after a restart so at least in my case i dont think it is simply a heap size /out of memory issue but it is certainly generating Java exception log files.

I did a clean install of Sage to eliminate plugins and no change ... Logs were captured and sent to Sage last night.... Lets hope they help with the analysis. At this point the family are afraid to watch TV when i am not home so i hope its an easy fix.

Additional system info ... in the interest of full disclosure ..... Te OS in Win7 32 bit and the additional tuners are FIOS STBs connected via firewire.....

[panteragstk]

Have either of you submitted a bug request.

[barney B.A.]

Originally Posted by bmh

Also, I just installed SJQ4 a few days ago so I wouldn't think that would be the culprit either. I'd really hate to disable the plugins as the WAF will plummet

I had memory leak issues when I had sjq4 installed. I had to uninstall and my memory problems went away.

[bmh]

Updating the Java software from v10 to v24 seems to have helped. The heap size now fluctuates from 400mb to 800mb where before it would stay in the 900mb to 1gb range.

[FlyingDoc]

Originally Posted by panteragstk

Have either of you submitted a bug request.

Yes .. hence the statement "i have been working a bug with Sage"

They reviewed the logs and based on that suggested updating the Intel Video Driver.....Note in my case something was producing a crash log called hs_err_pidXXXX.log. From this Sage Support determined the module apparently responsible and identified it as an intel driver module.

This update was done earlier this evening ..... still testing the stability but i have been able to skip backwards and forwards on a couple of test recordings without a crash ..... more testing tonight ... i'll provide another update later.

OK i have run the system all evening with no crashes .... This has definitely improved the stability for me... Thanks Sage Support!

[panteragstk]

Originally Posted by FlyingDoc

Yes .. hence the statement "i have been working a bug with Sage"

They reviewed the logs and based on that suggested updating the Intel Video Driver.....Note in my case something was producing a crash log called hs_err_pidXXXX.log. From this Sage Support determined the module apparently responsible and identified it as an intel driver module.

This update was done earlier this evening ..... still testing the stability but i have been able to skip backwards and forwards on a couple of test recordings without a crash ..... more testing tonight ... i'll provide another update later.

OK i have run the system all evening with no crashes .... This has definitely improved the stability for me... Thanks Sage Support!

Yeah, I was asking a general question that didn't apply to you. Sorry. Glad it works though.

[bmh]

Originally Posted by panteragstk

Have either of you submitted a bug request.

I was planning on submitting a bug if the respones from this thread indicated it was indeed a bug. So far, it seems like Java was the culprit. I'll do some more testing and report back later

[appelm]

Originally Posted by bmh

Ever since I installed 7.1.7, I've been having issues with SageTV just randomly closing. I thought it may be due to the Java heap size so I changed it to 1024mb but that didn't seem to help. Last night after watching a recorded show, I hit exit on my remote and it crashed. There's no warning or message, SageTV justs closes. The one thing I've noticed is that power cycling the extenders seems to quickly max the Java heap and speed up the frequency of the crashes. Anyone else having this issue?

I've been noticing random closes too lately. I'll turn on the TV hooked up to the extender and Sage won't come up. Upon checking the server, I'll SageTV isn't running.

[bmh]

It's been 4 days since I updated Java and I have had zero issues with memory or random crashes

[lotusvball]

I was having constant Out of memory issues with version 7.17. I tried disabling some of my plugins, but could find the one(s) causing the problem, so I reverted back to Sage 7.15 and now the problem is gone. I will not upgrade until the figure out the issue with the plugins. And no I didn't submit a bug report. I do not have the time to run all the logs and send everything in. If I get the time at a later date I might do this but I need it to just work so I will stay away from beta for a while.