Lock ups at 1:08

[co30cl]

Hi,
I have the previous generation HD Theater box and when playing movies it always locks up at 1:08. If I press the stop button it'll sometimes come back, but generally requires a power cycle. Anyone else have this problem or know how to fix it? Thanks. BTW: I have the latest verison firmware and server software.

[timd]

I have an HD100 that has always had this problem as well as a problem with stuttering video. On Wednesday the HD100 died due to the bad capacitor problem. Today I replaced the bad caps and it's working again - the stuttering video is gone, but the 1:08 hang is still there.

I've never thought to see at what time it does this, but today after watching a movie to test my repairs, it hung at 1:08! I'm running the latest FW and SageTV software as well. I've had this unit for a couple years now. I have my media stored on a ReadyNAS and play videos over the home network (wired).

[popcorndog]

I run Sage on Windows Home Server, so this may or may not apply. I did notice that I would get consistent lockups or hanging at certain times. I determined that they occured on Java auto update, Windows update, and Windows back up operations. I have since turned off Java and Windows auto updates and moved the back up operation to the wee hours of the morning.

I would look to see if your storage device or computer is performing some regular activity at that time.

[co30cl]

After troubleshooting for a while and trying several things, this is still an issue. BTW: 1:08 is not the time of day, its the duration into the movie being played.

When it locks, the server computer is still running fine and hardly and CPU/memory resources being used. There's absolutely nothing running on it other than Sage (no apps, updates, scans, etc). I also tried stopping a few uneeded services, that didn't help. I also bought a new network card and switch, that didn't help either. I'm pretty computer literate and this is driving me crazy. Since noone else is reporting this, I'm looking at my server computer as the root but can't figure it out. Any ideas are appreciated.

[JetreL]

Wow 7 months to respond to a post. Anyway!

If it's the same video having an issue there is probably something wrong with the file. I would replay the video with Debug turned on and open a ticket with Sage. With the logs

If it is all videos then you are probable having an issue with heat or some other similar type of issue. I would open up the casing to see if there are any popped or bulging capacitors. Also, you may want to try running it without any casing to allow for airflow. (Will probably void any warranties and make sure you use safety precautions.)

Also update SageTV to the latest greatest to see if that resolves the issues.

Hope this helps!

[co30cl]

Problem is with all movie files, pretty sure heat isn't an issue, and running ver 6.6 (I've has this problem since I got the setup several versions ago, in each version). How do I turn on debug and how do I look at it? Thx.

[robogeek]

Debug logging can be turned on at Setup->Detailed Setup->Advanced->Debug Logging. After enabling debug logging, you'll need to restart SageTV. You should get files sagetv_?.txt where ? is 0-3. Each restart will start a new log, where sagetv_0.txt is the most recent log file. When a log file reaches approximately 9MB, it the log files will be renamed and a new sagetv_0.txt is started. When you play a movie and it stops, take note of the time (clock time, not file play time) the error happens. You can load the sagetv_0.txt log file in Notepad and scroll down to the approximate time the error happened and look for any errors. Or just attach the log here (or zip it up if it's too big) and one of us can take a look at it and see if anything jumps out.

[metapath]

I just found this thread. I started having this same problem when I installed the 7.09 beta. Happened again with 7.10 beta. With the WAF going down the tubes, I finally submitted a bug report when 7.11 beta still had the same lockups. Happens with Sage recordings, DVD rips to folder, ISO rips, heck...it even happens during Photo slideshows in screensaver mode.

Still using the same server (win XP Pro) with two HD-200s and it happens on both...so I'm pretty sure this is a beta issue (never once had a lockup running Sage 6.x).

I enabled logging last night (after I got a lockup 5 seconds into a movie) so no joy yet...but I'm confident this will get fixed.

[co30cl]

I watched a movie this weekend and it hung as always. Here's the log starting at the time the hang occured:

Sat 7/10 20:46:10.434 [EventRouter-001e40b59fe1@1d4bee1] VF.submitJob(VFJob[CloseMF r=0.0 t=0 file=null ifn=null])

Sat 7/10 20:46:10.434 [VideoFrame-001e40b59fe1@4f12c2] VF processing job VFJob[CloseMF r=0.0 t=0 file=null ifn=null] nPlayin=true

Sat 7/10 20:46:10.434 [VideoFrame-001e40b59fe1@4f12c2] VF processing on UI Thread VFJob[CloseMF r=0.0 t=0 file=null ifn=null]

Sat 7/10 20:46:11.837 [AWTThreadWatcher-001e40b59fe1@ed889d] EventThread-001e40b59fe1 Hang Detected - hang time = 750

Sat 7/10 20:46:12.335 [FinalRender-001e40b59fe1@198c706] ImageUtils loading URL jar:file:/C:/Program%20Files/SageTV/SageTV/Sage.jar!/images/tvicon_anim3.png

Sat 7/10 20:46:12.338 [FinalRender-001e40b59fe1@198c706] ImageUtils creating BI copy sun.awt.image.ToolkitImage@f20bb6 w=121 h=121 freeMem=16906784 totalMem=124620800

Sat 7/10 20:46:12.338 [FinalRender-001e40b59fe1@198c706] ImageUtils creating scaled masked copy width=43 height=43 option=null BufferedImage@18625e5: type = 2 DirectColorModel: rmask=ff0000 mask=ff00 bmask=ff amask=ff000000 IntegerInterleavedRaster: width = 121 height = 121 #Bands = 4 xOff = 0 yOff = 0 dataOffset[0] 0

Sat 7/10 20:46:12.587 [AWTThreadWatcher-001e40b59fe1@ed889d] EventThread-001e40b59fe1 Hang Detected - hang time = 1500

Sat 7/10 20:46:13.337 [AWTThreadWatcher-001e40b59fe1@ed889d] EventThread-001e40b59fe1 Hang Detected - hang time = 2250

Sat 7/10 20:46:14.087 [AWTThreadWatcher-001e40b59fe1@ed889d] EventThread-001e40b59fe1 Hang Detected - hang time = 3000

Sat 7/10 20:46:14.837 [AWTThreadWatcher-001e40b59fe1@ed889d] EventThread-001e40b59fe1 Hang Detected - hang time = 3750

Sat 7/10 20:46:15.587 [AWTThreadWatcher-001e40b59fe1@ed889d] EventThread-001e40b59fe1 Hang Detected - hang time = 4500

Sat 7/10 20:46:16.337 [AWTThreadWatcher-001e40b59fe1@ed889d] EventThread-001e40b59fe1 Hang Detected - hang time = 5250

Sat 7/10 20:46:17.087 [AWTThreadWatcher-001e40b59fe1@ed889d] EventThread-001e40b59fe1 Hang Detected - hang time = 6000</PRE>