SageMC 6.2 bug: AWTThread Hang Detected & Standby

[CadErik]

I looked more in details why with SageMC my Media Center is not going in Standby mode. After digging in the logs here is what I find:

Wed 11/8 21:17:36.342 AWTThread Hang Detected - hang time = 750
Wed 11/8 21:17:37.092 AWTThread Hang Detected - hang time = 1500

This happens periodically.

Anyway to diagnose this further??
I'm running the latest JRE 6, but I also tried with JDK 1.5.0_09 and no changes :-(
I have SageTV in service mode.

Thanks,

Erik.

[MeInMaui]

I have seen this on numerous occasions on both my server and my client with JRE 1.4.2_6 and 1.4.2_11. I can't say what is causing it, but it always seems to be there when I have hangs. Anyway, here is a thought. Is it possible that the logging itself is what is causing your computer to not enter standby? I bet every time it writes an event out to file it resets the inactivity timer (if there is such a thing). I'm probably out to lunch on this, but I thought I'd mention it anyway.

Aloha,
Mike

[dflachbart]

Originally Posted by CadErik

I looked more in details why with SageMC my Media Center is not going in Standby mode. After digging in the logs here is what I find:

Wed 11/8 21:17:36.342 AWTThread Hang Detected - hang time = 750
Wed 11/8 21:17:37.092 AWTThread Hang Detected - hang time = 1500

This happens periodically.

Anyway to diagnose this further??
I'm running the latest JRE 6, but I also tried with JDK 1.5.0_09 and no changes :-(
I have SageTV in service mode.

Thanks,

Erik.

Wed 11/8 21:26:32.658 AWTThread Hang Detected - hang time = 747
Wed 11/8 21:26:33.405 AWTThread Hang Detected - hang time = 1494
Wed 11/8 21:26:34.155 AWTThread Hang Detected - hang time = 2244
Wed 11/8 21:26:34.905 AWTThread Hang Detected - hang time = 2994
Wed 11/8 21:26:35.655 AWTThread Hang Detected - hang time = 3744
Wed 11/8 21:26:36.277 setUI(sage.b1@1f81e2d[Xtra: Custom Menus by malore]) histIdx=9 uiHistory=[sage.b1@123a510[Library], sage.b1@20a02d[Main Menu], sage.b1@1e3606d[Xtra: SageTV Recordings by malore], sage.b1@20a02d[Main Menu], sage.b1@136d8e4[LiveTVGuide w/ Optional Preview], sage.b1@20a02d[Main Menu], sage.b1@1aa6088[Schedule Recordings], sage.b1@1f81e2d[Xtra: Custom Menus by malore], sage.b1@11a0fb[Xtra: Multimenu by malore], sage.b1@1f81e2d[Xtra: Custom Menus by malore]]
Wed 11/8 21:26:36.297 Calculate space required for upcomming manual/favourite airings for next 2 days and display
Wed 11/8 21:26:36.401 AWTThread Hang Detected - hang time = 4490
Wed 11/8 21:26:36.570 Calculate size of partial recordings
Wed 11/8 21:26:36.574 Found 0 partials using 0 bytes

This is an excerpt using the default STV ...
These 'Hang' messages are just normal and don't point to an issue per se

Dirk

[dflachbart]

Originally Posted by MeInMaui

Anyway, here is a thought. Is it possible that the logging itself is what is causing your computer to not enter standby? I bet every time it writes an event out to file it resets the inactivity timer.

Aloha,
Mike

Mike, good point. If Erik is using the beta this could be a potential cause, since debug logging can not be disabled.


Dirk

[CadErik]

Originally Posted by flachbar

Mike, good point. If Erik is using the beta this could be a potential cause, since debug logging can not be disabled.

Hmmm I'm not an expert in power saving on windows but I would have assumed that only user actions (mouse or keyboard) would keep the system up.
I don't have these error messages on the standard STV though. This doesn't sound good to me anyway that there would be an AWT thread hung...

Erik.