Frequent Crashes

[keodark]

I really want to like SageTV... I really want to buy it when my 21-day trial ends... but I'm experiencing quite a litany of problems with the software (mostly stability problems). Here's the latest, a crash while changing channels in Live TV.

I'm using a single HDHR, ATSC over-the-air programming (digital) on both tuners. I have no extenders, no mods/plugins, and I'm not running the server. I have configured Sage to run as a service, using the GUI in the install directory. (Should I not have done that?)

AMD 5050e, Gigabyte MA78GM-US2H, onboard lan, onboard audio, 2x1gb ddr2, ATI Radeon HD 4670, recording on 2nd (non-OS) partition of a 1TB WD Green HD. Windows XP (clean install).

Here's the end of the debug log from my latest crash:

Thu 3/26 14:38:13.834 Seeker awoken
Thu 3/26 14:38:13.834 MemStats: Used=15MB Total=22MB Max=266MB
Thu 3/26 14:38:13.834 MARK 1 currRecord=FA[stationID=20451 The Bonnie Hunt Show time=Thu 3/26 14:00:00.000 dur=1:00:00] enc=Silicondust HDHomeRun Tuner 10164DA4-1 clients=[] ir=false
Thu 3/26 14:38:13.835 Seeker in AUTOMATIC mode nextRecord=null nextTTA=9223372036854775807
Thu 3/26 14:38:13.835 newRecord=FA[stationID=20451 The Bonnie Hunt Show time=Thu 3/26 14:00:00.000 dur=1:00:00]
Thu 3/26 14:38:13.835 Record was enabled on what's already being recorded; update status.
Thu 3/26 14:38:13.835 Keeping record just the way it is.
Thu 3/26 14:38:13.835 MARK 1 currRecord=null enc=Silicondust HDHomeRun Tuner 10164DA4-0 clients=[] ir=false
Thu 3/26 14:38:13.835 Seeker in AUTOMATIC mode nextRecord=null nextTTA=9223372036854775807
Thu 3/26 14:38:13.835 newRecord=null
Thu 3/26 14:38:13.835 NOTHING TO RECORD FOR NOW...
Thu 3/26 14:38:13.836 RootFile=D:\ fstype=NTFS fileLength=1665576960
Thu 3/26 14:38:13.836 Checking video directories for new files
Thu 3/26 14:38:13.837 Diskspace checking is running
Thu 3/26 14:38:13.837 Verifying existence of all TV media files in database fixDurs=false avoidArchive=true
Thu 3/26 14:38:13.838 Enforcing keep at most limits for the files...
Thu 3/26 14:38:13.838 Seeker clearing unwanted and partial files...
Thu 3/26 14:38:13.838 needFreeSize = 0.801 GB currFreeSize=619.380618752 GB
Thu 3/26 14:38:13.838 Seeker waiting for 21 mins.
Thu 3/26 14:38:15.790 Error with c/s comm:java.lang.NullPointerException
Thu 3/26 14:38:15.790 NetworkManager CommunicationFailure : /127.0.0.1:1032 type=2
Thu 3/26 14:38:15.790 NetworkManager CommunicationFailure : /127.0.0.1:1032 type=2
Thu 3/26 14:38:17.730 Error communicating with server:java.lang.NullPointerException
Thu 3/26 14:38:17.731 Cleaning up c/s connection
Thu 3/26 14:38:17.731 NetworkManager CommunicationFailure : /127.0.0.1:1032 type=1
Thu 3/26 14:38:17.731 MsgSend thread terminating for /127.0.0.1:1032

Thoughts? Should I provide more detail on my settings, etc?

[GKusnick]

To clarify: when you say you're not running the server, you mean you have SageTV Server set to Disabled in Detailed Setup > Server, is that correct?

But you do have it configured to run as a service, which means that the UI runs in a different process. So which process is it that's crashing, the service (SageTVService.exe) or the UI (SageTV.exe)? And which log did you post, the service log (sagetv_0.txt) or the UI log (sagetvclient_0.txt)? From your description, I'm guessing it's the UI that's crashing, but the log you posted looks like a service log.

[keodark]

Thanks for the quick followup. I'm still not sure if I should be running Sage as a Service (I saw a thread at one point that indicated it might solve a problem that I was having at the time).

To answer your questions-
Correct, SageTV Server is Disabled.
The UI Crashed. (The service is actually still running), and the log I posted was from sagetv_0.txt ... there is no server log. I don't see a service log in the Sage install directory either.

The only sage.properties change I've made is:
debug_logging=TRUE

-Keo

[stanger89]

We'll need the sagetvclient_0.txt then since it's the UI that crashed. You'll need to enable debug logging in the sageclient.properties file for that to be created.

I'm guessing it's a decoder issue that's killing your client though. What decoders do you have selected in Detailed Setup->Video and Audio sections?

[Opus4]

The full sagetv_0.txt and sagetvclient_0.txt files would be more useful for someone to look at. The client log is mentioned above, but I would liek to see the full service log. You can zip & attach the files to a post.

Is the service actually exiting/crashing? For the service, Windows may have an event log to check out too.

Are you using network paths for recording dirs? If so, the service has to log in as a user w/a password with permission to access the paths & the paths have to be UNC paths, not mapped drive letters.

If you go to the System Info page, you can use the Info command after the menu stops updating to write SystemInfo.txt in your SageTV directory. That would give more info about your system.

- Andy

[GKusnick]

Originally Posted by keodark

I'm still not sure if I should be running Sage as a Service...

I'd recommend it, unles you have some compelling reason not to. The service logs in and can start recording as soon as Windows boots up, before anybody logs in to the desktop. And if the UI does become unstable (as yours is now), that won't impact the service's ability to keep recording. Generally, the more third-party tweaks and UI mods you add to your UI, the more reason you have to run the recording engine as a service where it's immune to UI crashes.

[keodark]

What decoders do you have selected in Detailed Setup->Video and Audio sections?

A wealth of feedback already! Let's see what I can offer-

First, I only enabled the sage.properties logging. I wasn't aware that running Sage as a Service meant that the Sage Client would be running. I'll add the debug property to the SageClient.properties file for future crashes.

Decoders: Renderer: VMR9 (I changed because Overlay was causing stuttering)
MPEG2 Vid Decoder Filter: SageTV MPEG Video Decoder (default)
DXVA: Yes (A recent change, I was hoping to eliminate the stuttering mentioned above)
MPEG4 Playback: DirectShow (default)
Audio Renderer: Default
MPEG2 Audio Decoder filter: SageTV MPEG Audio Decoder

After I post this, I'm going to go do some reading on these settings, as I don't know if I should be using the ATI equivalents, or if I should install new codecs, or if I want DXVA, etc.

I am not referencing any networked drives. The Media Center and Recording directories are both on the second partition of the single SATA hard drive (partition 1 is Windows XP).

-Keo

[keodark]

Originally Posted by GKusnick

I'd recommend it, unles you have some compelling reason not to. The service logs in and can start recording as soon as Windows boots up, before anybody logs in to the desktop. And if the UI does become unstable (as yours is now), that won't impact the service's ability to keep recording. Generally, the more third-party tweaks and UI mods you add to your UI, the more reason you have to run the recording engine as a service where it's immune to UI crashes.

Excellent! I'm glad to know this, thank you.

[keodark]

Hey all,

I'm running my trial version - day 2 - of Sage in Service mode, and occasionally, the SageTV app will come out of Sleep into fullscreen black and stops responding to input. I can alt+tab and access the Task Manager, but Sage doesn't respond to anything, and I have to force quit it. SageTVService process seems unaffected.

I'm using a single HDHR, ATSC over-the-air programming (digital) on both tuners. I have no extenders or placeshifters, no mods/plugins, no networked drives, and I'm not running the server. HTPC is: AMD 5050e, Gigabyte MA78GM-US2H, onboard lan, onboard audio, 2x1gb ddr2, ATI Radeon HD 4670, recording on 2nd (non-OS) partition of a 1TB WD Green HD. Windows XP (clean install).

The usual files are attached.

Here are the tails of both log files:
sagetvclient_0.txt:

Thu 3/26 22:06:19.065 Screen Saver Timeout expired....tv=false playin=false fs=true sleepy=true currSS=false
Thu 3/26 22:10:35.873 VF processing job null nPlayin=false
Thu 3/26 22:10:35.873 VF thread is now waiting for 0:00:00.000
Thu 3/26 22:12:49.266 setUI(sage.b1@ea276d[Schedule Recordings]) histIdx=0 uiHistory=[sage.b1@ea276d[Schedule Recordings]]
Thu 3/26 22:12:55.613 processOptionsMenu optionsMenu=default:BASE-51512|OptionsMenu:VideoMenuOptions
Thu 3/26 22:12:56.741 ERROR 'IN' rendering op was lost in the animation system!!!
Thu 3/26 22:13:00.157 processOptionsMenu optionsMenu=default:BASE-51512|OptionsMenu:VideoMenuOptions

sagetv_0.txt:

Thu 3/26 22:14:30.114 NOTHING TO RECORD FOR NOW...
Thu 3/26 22:14:30.114 Checking video directories for new files
Thu 3/26 22:14:30.116 Diskspace checking is running
Thu 3/26 22:14:30.116 Verifying existence of all TV media files in database fixDurs=false avoidArchive=true
Thu 3/26 22:14:30.116 Enforcing keep at most limits for the files...
Thu 3/26 22:14:30.117 Seeker clearing unwanted and partial files...
Thu 3/26 22:14:30.117 Seeker waiting for 153722846645398 mins.
Thu 3/26 22:14:33.259 Error with c/s comm:java.lang.NullPointerException
Thu 3/26 22:14:33.260 NetworkManager CommunicationFailure : /127.0.0.1:1043 type=2
Thu 3/26 22:14:33.260 NetworkManager CommunicationFailure : /127.0.0.1:1043 type=2
Thu 3/26 22:14:34.384 Error communicating with server:java.lang.NullPointerException
Thu 3/26 22:14:34.385 Cleaning up c/s connection
Thu 3/26 22:14:34.385 NetworkManager CommunicationFailure : /127.0.0.1:1043 type=1
Thu 3/26 22:14:34.385 MsgSend thread terminating for /127.0.0.1:1043

Any suggestions? I'd very much like to get a stable, simple build of Sage going so I know I don't have to start looking for an alternative stable PVR

-Keo

[Opus4]

Originally Posted by keodark

I'm running my trial version - day 2 - of Sage in Service mode, and occasionally, the SageTV app will come out of Sleep into fullscreen black and stops responding to input. I can alt+tab and access the Task Manager, but Sage doesn't respond to anything, and I have to force quit it. SageTVService process seems unaffected.

By sleep, it looks like you mean it goes into the full-screen screen saver, right?

Are you using Full Screen Exclusive mode? If so, try disabling that.

I would check for some updates: see if DirectX is up to date, see if there is an updated video card driver, and install the latest Java (making sure SageTV is not running, including the service). Also, there is a newer beta version of SageTV in the beta section of the forum.

- Andy

[keodark]

Originally Posted by Opus4

By sleep, it looks like you mean it goes into the full-screen screen saver, right?

Are you using Full Screen Exclusive mode? If so, try disabling that.

I would check for some updates: see if DirectX is up to date, see if there is an updated video card driver, and install the latest Java (making sure SageTV is not running, including the service). Also, there is a newer beta version of SageTV in the beta section of the forum.

- Andy

Sorry, once again I didn't provide enough context for my issue.

I'm using the "sleep" setting that sleeps Sage in the taskbar, so that I can use Windows for other things. I generally do this from fullscreen (not FSE) using the Standy menu item. This works rather well unless I leave it in the taskbar for more than an hour or so (that's a guess), then this happens when I try to Restore it.

Full Screen Exclusive mode is turned off.

Directx is 9.0c (4.09.0000.0904)
Java SE RTE is 1.6.0_10
I installed the latest ATI Catalyst and drivers for my card from the website when I set up the computer (Monday). Same goes for all the other drivers on the pc.

Can the beta be run as Trial mode? I can give it a shot, although I'd hate to destabilize my system even further by running beta code.

One question that might help me - I'm using the SageTV MPEG decoder filter. Should I enable the ATI MPEG decoder filter instead? I know that's unlikely to cause this particular UI issue, but in general is it better to use Sage's or the video card chipset provider's version of the decoder?

Also, might I have more luck with the Overlay renderer?

Thanks,
-Keo

[keodark]

I just managed to repeat this particular issue! Here's the steps to reproduce (on my machine, anyway):

1) Enter fullscreen (not FSE) on Sage TV UI.
2) Click 'Standby' in main menu. (Settings cause it to sleep in the notification area on the far right of the taskbar)
3) Wait 5 minutes for Windows screensaver to launch (default Windows XP screensaver)
4) Move the mouse to exit screensaver
5) About 1/4 of the time, Sage TV now has a button at the bottom of the screen (in the normal taskbar area), not just the little icon in the notification area! Click on this (or 'launch' SageTV.exe by shortcut, which is what my iMon remote uses to launch Sage), and you get fullscreen black, unresponsive Sage. I can alt+tab or ctrl+alt+del.

Task Manager shows SageTV as running, does not indicate a problem.

Note that my Windows Power Management settings are:
Turn off monitor: 20 minutes
Turn off hard disks: Never
System standy: Never
Hibernation: Disabled

Attached is sagetvclient_0.txt from -after- the fullscreen black, but -before- I forcequit the executable.

Edit (Followup): This doesn't always happen - the SageTV icon does not always appear in the normal taskbar after cancelling the Windows screensaver. Also, when it *does* happen, right-clicking the Notification Icon and clicking "Restore SageTV" brings up Sage correctly.

-Keo

[Opus4]

Yes, you can use the beta as part of the trial.

I haven't heard of the the symptoms you described, so I asked SageTV about it. They didn't see anything in the logs either & asked that you grab a screenshot of the next time it happens so they can see what it looks like with SageTV in both the system tray and the taskbar. Maybe it would be good to also have Task Manager open, sorted by Image Name w/the SageTV processes visible. If you could save the screen shot as a jpg file, you could attach that to a post.

- Andy

[keodark]

Here you go. I had to wake+sleep Sage and wait 1 minute for Windows screensaver 4-5 times before it happened:

[Opus4]

The SageTV window shouldn't be visible like that when it is in the system tray. Try setting this property in SageClient.properties:

dispose_windows=true

- Andy

[keodark]

Thanks.

I put the property in (I exited the sage client first). It was "false" before. Note: I'm still running the public release - I haven't braved the beta yet.

I'll let you know if I see the issue again.

-Keo

[judoGTI]

Hye guys -

I've been having a similar issue. I notice mine most when I come back from a sleep (SageTV in screensaver mode, or WinXP in screen saver mode).

Often if I am watching a recording and hit the stop button SageTV will close out 100% (no crash, but its as if someone killed the processes). Sometimes this also occurs if Im watching a show and get to the end, hit stop and then choose to delete that recording, when I click "Delete this recording now" it will close out (and not delete the recording).

Now I do not want to threadjack because it seems like my issue is different than the OPs I just wanted to ask what log files should I gather? Will they be different since I don't get a crash message (The SageTV has crashed, report it to Microsoft pop up window).

If I can find the right logs to collect I will start a new thread. Thanks.