5.0.2 Crashes

[95TBird]

Well, I Installed Java 1.5.0_05 3 days ago & all the "Crashes to Desktop" have stopped.

I was getting them at least daily & I could make one happen by putting Sage to Sleep & then letting the PC go into sleep mode. So far so good!!

I'm also still running VMR9 & FSE !! Life just keeps getting better !!

Bruce

[Wheemer]

i'm also have pretty good luck with the java 1.6.0 beta

I've had one crash that I think was a network traffic problem.

[HawgGuy]

Just tried JRE 1.6 beta myself - Number of handles open started at around 7000 and was at 150000 and growing when I shut it down. Slipped back to JRE 1.4.2 and all is well - stable at around 6800 handles.

[AtariJeff]

<fingers crossed>Since I downgraded no crashes this weekend.

[bitbyte]

This weekend I updated all of my pvr250 drivers and decoders, my motherboard drivers, video card etc. plus i down-rev'd my java to release 5. The only issue I've had is one that I had before doing all of this.

Sometimes when I'd go to watch a live show, or a recorded show, the audio would screech really loud, then sagetv would crash to the desktop. Sometimes restarting sagetv would fix it. Sometimes a reboot would. Other times nothing would fix it and i'd have to delete the recording.

I did have this happen on one recording after I updated everything, but I suppose it could have been something wrong with the recording itself. not sure... It hasn't happened since then. Time will tell. I don't think this issue was related to the other crash to desktop issue I was having tho, it would just drop out in the middle of watching something with no warning at all.

[emok]

I've been getting crashes more often with 5.0.2 as well. These are typically accompanied by an Error in the eventvwr Application logs. I don't have the exact wording, but it basically says "error cause by sagetv.exe, fault module is jvm.dll" with some version number. I'll try to capture the exactly logs later. Is anyone else getting these errors in their eventvwr logs?

I was getting leaking handles previously but then uninstalled my 1.4.2_06 and 1.5.0_06 JREs and went to 1.5.0_05 and that problem was solved.

EDIT: I actually meant my leaking handles problem was solved, but NOT my application errors. I'm still getting these, perhaps once a day. No hs_err log files and nothing coming up on sageclient_0.txt.

[stevech]

Originally Posted by emok

I was getting leaking handles previously but then uninstalled my 1.4.2_06 and 1.5.0_06 JREs and went to 1.5.0_05 and that problem was solved.

Lots of people talking about leaks in JRE.

Sage needs to take a position on what will work correctly with Sage 5.

[Narflex]

Originally Posted by stevech

Lots of people talking about leaks in JRE.

Sage needs to take a position on what will work correctly with Sage 5.

WE HIGHLY RECOMMEND USING JAVA 1.5.0_05 FROM SUN. DO NOT USE JAVA 1.5.0_06, IT HAS KNOWN LEAKS IN IT.

You can get Java 1.5.0_05 from here:
http://java.sun.com/products/archive..._05/index.html

We'll be putting out a new installer shortly that has 1.5.0_05 included in it.

[emok]

Originally Posted by Narflex

Still looking to see if anyone has had a crash like this since switching to Java 1.5.0_05....so far the theory that 1.5.0_06 is causing the crashes is still holding....

Jeffrey,

I'm still having this problem and I'm running 1.5.0_05. I'm running sage in service mode. My UI still has the crashes. I mentioned in an earlier post that I have the client debug logs enabled but they don't seem to show anything. I also don't see any hs_err files. I DO have Error events in the windows eventvwr.

[Narflex]

Originally Posted by emok

Jeffrey,

I'm still having this problem and I'm running 1.5.0_05. I'm running sage in service mode. My UI still has the crashes. I mentioned in an earlier post that I have the client debug logs enabled but they don't seem to show anything. I also don't see any hs_err files. I DO have Error events in the windows eventvwr.

Please set the property debug_logging=TRUE in your SageClient.properties file while SageTV is NOT running. Then start it up again and it should create a sagetv_0.txt log file. Post that here please. You don't need to wait for a crash. I first want to check if you actually are running Java 1.5.0_05.

[emok]

I've attached my sagetvclient_0.txt file. It looks like it's using the correct vm version.

I've been searching for possible reasons for these crashes. Could it have something to do with the dual core issues with nvidia drivers? http://www.hardforum.com/showthread.php?t=983781 Alternate #4? This problem is also noted in the release notes.

I'll try that registry fix and see if I have more issues.

[Narflex]

Originally Posted by emok

I've attached my sagetvclient_0.txt file. It looks like it's using the correct vm version.

I've been searching for possible reasons for these crashes. Could it have something to do with the dual core issues with nvidia drivers? http://www.hardforum.com/showthread.php?t=983781 Alternate #4? This problem is also noted in the release notes.

I'll try that registry fix and see if I have more issues.

That's interesting....we've got a lot of data from people to show that 1.5.0_05 fixes the crashing to desktop issues they've had. Looks like you may have a different variant of it (again with the NVidia decoder). I'll have to contact NVidia about this....they're starting to make us look bad.

[Kirby]

I switched from 1.5.0_06 to 05 last night, and within 10 minutes had a UI crash. Dont know if its coincidence or not, but using Nvidia decoder, Nvidia vid card, and amd dual core (on nvidia NF4 mb). And that crash was while just navigating the menus in the UI. Then a few hours later, when I was watching a recorded show, it crashed again.

I'll have to clear out my log files, and start a fresh one and hope for a crash relatively soon, because for some reason my log files run about 8-10mb per day, way too much to post one here.

[emok]

After I got home yesterday I made two changes.
1. Removed my USB wireless network adapter.
2. Made the registry modifications as specified in the nvidia Forceware 84.21 release notes for dual-core issues.

Last night I watched several episodes. Various content. American Idol HD, Scrubs HD, and some SD content. No crashes so far (crossing my fingers).

Will try again later tonight and keep you posted.

EDIT: As an aside, I've been using sage for a few years now and it's been quite solid. I recently moved the sage install to a dual-core system that I built. Most of my issues have started after this move to dual core. Granted, there are many variables that have changed so it's hard to pinpoint what exactly the problem might be (buggy onboard video/bad RAM/driver issues with dual core/etc.). Unfortunately, this is also the time that I upgraded to Sage 5.0.x, so that adds another variable into the mix.

For those who have had this crashing problem even with JRE 1.5.0_05, are you using Dual Core or HT processors with Nvidia graphics cards/drivers?

old system:
ECS 755-A2 (s754)
Athlon 64 3000+
Geforce 6200 AGP
Nvidia Forceware 84.21 drivers
Nvidia Purevideo decoder .196
1GB Single-Channel DDR (2 sticks of different branded memory)
2x pvr 150
1x pvr 500

new system:
MSI K8NGM2-FID (s939)
Athlon 64 X2 3800+
Onboard Geforce 6150
Nvidia Forceware 84.21 drivers
Nvidia Purevideo decoder .196
1GB Dual-Channel DDR (Corsair Value Select Kit)
1x pvr 150
1x pvr 500
sgraphrecorder w/DCT6200

[Kirby]

Asus A8N-SLI Premium (nForce 4 northbridge)
AMD X2-3800+ dual core
BFG 7800GTX PCI-E 256mb vid card
NForce 84.21 drivers
NVidia PureVideo 1.02-196 (Gold)
1GB DDR
JRE 1.5.0_05
Sage server 5.0.2 w/ VMR9, 3D on, FSE mode, not using service mode
2 R5000 network encoders (locally connected USB)
1 DCT-6200 firewire network encoder (locally connected)
1 Fusion 5 OTA PCI tuner
1 MSI TheatrePro 550 PCI

Getting crashes now, and was with 1.5.0_06 as well, not viewing from a client. Didnt have issues with 4.1.11 and prior in terms of crashing, in fact I cant ever remember a crash from my first version (4.1.3). I too will try the reg hacks for the dual core setup tonight.

Other anomolies I have recently experienced, which all may be JRE related:

1) using only UNC path recording directories (local or remote to server) all recording directories would randomly disappear for 30 seconds (thus screwing up any recordings in progress).

2) Sage Server UI crashes in 5.0.2 (previously used 4.1.11)

3) all network encoders disappear for 30-60 seconds (again makes a real mess of the recordings!). This includes 2 R5000 network encoders, and 1 DCT-6200 firewire network encoder, all connected locally to the Sage server.

[roxy99]

Java 1.4 works great on 5.0.2.
Java1.5 beta 6 gave me memory leak.

Since switching to 1.4, no problems at all.

[Kirby]

Do you have a link to access 1.4 Java? I cant find it.

Nevermind, just found it...

[emok]

Originally Posted by Kirby

Asus A8N-SLI Premium (nForce 4 northbridge)
AMD X2-3800+ dual core
BFG 7800GTX PCI-E 256mb vid card
NForce 84.21 drivers
NVidia PureVideo 1.02-196 (Gold)
1GB DDR
JRE 1.5.0_05
Sage server 5.0.2 w/ VMR9, 3D on, FSE mode, not using service mode
2 R5000 network encoders (locally connected USB)
1 DCT-6200 firewire network encoder (locally connected)
1 Fusion 5 OTA PCI tuner
1 MSI TheatrePro 550 PCI

Getting crashes now, and was with 1.5.0_06 as well, not viewing from a client. Didnt have issues with 4.1.11 and prior in terms of crashing, in fact I cant ever remember a crash from my first version (4.1.3). I too will try the reg hacks for the dual core setup tonight.

Other anomolies I have recently experienced, which all may be JRE related:

1) using only UNC path recording directories (local or remote to server) all recording directories would randomly disappear for 30 seconds (thus screwing up any recordings in progress).

2) Sage Server UI crashes in 5.0.2 (previously used 4.1.11)

3) all network encoders disappear for 30-60 seconds (again makes a real mess of the recordings!). This includes 2 R5000 network encoders, and 1 DCT-6200 firewire network encoder, all connected locally to the Sage server.

Kirby,

Are you using the nvidia firewall? Not sure if that would have anything to do with it, but it sounds like it may be somewhat related. I've read about some people having problems with it (http://www.neowin.net/forum/index.php?showtopic=326957).

[rickgillyon]

We're not all using nForce chipsets, are we?

Nowt but trouble in my experience...

[Kirby]

Originally Posted by emok

Kirby,

Are you using the nvidia firewall? Not sure if that would have anything to do with it, but it sounds like it may be somewhat related. I've read about some people having problems with it (http://www.neowin.net/forum/index.php?showtopic=326957).

Nope, didnt even install it.