EXCEPTION_ACCESS_VIOLATION

[nlaslett]

Is anybody else experiencing this? Occasionally SageTV will halt and exit when it is in sleep mode and goes to start a recording. There is no indication except the Sage icon in the SysTray disapears when I mouse over it, and when I go to resume Sage it instead has to launch the application.

The error log reads, in part:

# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x774ec2c0, pid=3252, tid=3256
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_04-b05 mixed mode, sharing)
# Problematic frame:
# C [ole32.dll+0xc2c0]

I'm running Sage 2.2.8 in application mode, WinXP Pro, 768MB, 160GB HD, Hauppauge PVR-150, newest version of Java

The error occurs exactly as the show is supposed to start recording. There is no pattern to shows or times or channels. After the error, Sage is off-line and won't record anything until relaunched.

I never encountered this problem under v.2.1.10, and everything else in my system is clean. This problem occurs about 20% of the time, randomly. I've tried to weed out any external factors, and I can't identify any conflicts. I've tried various audio/video encoder combinations in the Detailed Setup screen without effect.

I hate to back-rev but I fear I may have no choice...

-Neil

[Opus4]

I would check to see if tech support can see anything from the error log and/or possibly try the v3 beta to see what it does. The beta will also output a detailed log of SageTV's actions.

- Andy

[karnal]

It might also be possible that your Java version is not playing nice with Sage.

I've seen a couple of other posts on here that the Java version can make a difference between a working Sage box and a non-working Sage box. Try rolling back to the version of Java that shipped with your copy of Sage, and don't allow any updates.....

Hope this helps.....

[nlaslett]

Thanks for the tips. Does anybody know the version of Java that ships with Sage 2.2.8? Or: What version are you running?

I'm running version 1.5.0 (build 1.5.0_04-b05), downloaded from Sun.

[mkanet]

I can confirm that I also get that error message when I update my Java version to the latest version (1.5.0_04-b05) and use SageTV 2.2.8. Within 15 minutes of use, I will get that same error message.

This is very reproducable on my system. If i revert back to 1.5.0 (update 3), the problem goes away. This is a problem with version 4 only and SageTV 2.2.8

The reason I didn't think it was a big issue was because I am now concentrating on Sage 3.0.5 bugs.

[nlaslett]

Thanks. FYI, I found the older version of Java at:

http://java.sun.com/products/archive..._03/index.html.

[nlaslett]

OK...Now I'm annoyed. I back-reved to Java 1.5.0 update 3. The problem got better, but not entirely. Java still crashes sometimes. I'm going on a trip soon and don't want my system to die the first day I'm gone. Using the Service mode doesn't work because it can't bring the computer out of sleep. This is buggy, and everything points to Sage. I understand that everybody is all excited about testing the new v3 beta, but can't we get the current shipping version working as well? And does anybody know if switching to an even earlier version of JRE will help? What version was used in the original testing?

[ke6guj]

If you are going on a trip, why not set the computer up to not sleep. It doesn't cost that much to run full-time, and you'd have less worries while gone?

[mkanet]

Average cost of a typical PC with 300W power supply to stay on 24/7 is roughly $1/day.

[nlaslett]

Yeah, of course you're right, but the crashing still bugs me... :-\