Media Portal freezes on wake (3 Viewers)

[regeszter]

From a disaster recovery standpoint, what is missing in MP is a logic that verifies the existence and/or accessibility of paths as defined in the respective mediaportaldirs.xml. I could imagine a polling process in say 5 sec intervals until the remote shares are accessible. MP should not launch plugins or its own databases before said paths are online.

I think switch to MySql may be better than support shared sqlite database.

Second option: restarts MP on resume.

 

[HTPCSourcer]

Here is a new set of logs. I ran with Seb's latest build and had deactivated TVSeries.

The result is different from the previous tests. This time Windows came up with a normal full screen standard MePo homescreen - not the ususal MePo on top of the desktop - however, the time showing is 22:48, i.e. when I sent the PC into standby yesterday. After that MePo is unfortunately unreactive, yet seems to continue to log, and stays like that.

 

[Sebastiii]

I see in log after the last resume :
[2015-11-20 06:54:32,927] [Log ] [MPMain ] [DEBUG] - PS: RESUMESUSPEND
[2015-11-20 06:54:33,112] [Log ] [MPMain ] [DEBUG] - Main: PBT_APMSUSPEND - set GUIGraphicsContext.State.SUSPENDING

It's to stop rendering (so mp act like freezed)

before that we have the :
[2015-11-20 06:54:32,778] [Log ] [MPMain ] [DEBUG] - Main: OnResumeSuspend - set GUIGraphicsContext.State.RUNNING
Tha permit to have MP responsive.

That's not logic lol.

 

[HTPCSourcer]

That's not logic lol.

Who dunnit? Not me!

What next?

 

[Sebastiii]

Looking MP code :
when it's suspending, we didn't have the code reached :
Log.Debug("Main: PBT_APMSUSPEND GUIGraphicsContext.currentScreen.Bounds {0}x{1}", GUIGraphicsContext.currentScreen.Bounds.Width, GUIGraphicsContext.currentScreen.Bounds.Height);

It's look like MP run some older previous code that can't be right like that part should be play in main thread.

Does PS do something bad ?

It just quick analyse and maybe not a correct one but it's look strange.

 

[HTPCSourcer]

Does PS do something bad ?

I can deactivate the PS if you think that there is value in testing this scenario. I have the day off, so the next result would be quick to be posted. I would then wait 90min before tryinig to resume.

@mm1352000 : It's a little bit alchemistic but short standby times cause no trouble.

 

[Sebastiii]

Yep could be nice to try
Maybe you can try to wake up from WOL it seems in your last log there is few times where your PC waked up.

And ofc, it could be nice to understand what happen and fixed it

 

[Sebastiii]

It goes to suspend :
[2015-11-19 22:48:58,343] [Log ] [MPMain ] [DEBUG] - Main: PBT_APMSUSPEND GUIGraphicsContext.currentScreen.Bounds 1920x1080
[2015-11-20 03:32:38,472] [Log ] [MPMain ] [DEBUG] - Main: PBT_APMSUSPEND GUIGraphicsContext.currentScreen.Bounds 1920x1080
[2015-11-20 04:09:24,935] [Log ] [MPMain ] [DEBUG] - Main: PBT_APMSUSPEND GUIGraphicsContext.currentScreen.Bounds 1920x1080
[2015-11-20 05:14:05,562] [Log ] [MPMain ] [DEBUG] - Main: PBT_APMSUSPEND GUIGraphicsContext.currentScreen.Bounds 1920x1080

And here no log line but

[2015-11-20 06:54:33,112] [Log ] [MPMain ] [DEBUG] - Main: PBT_APMSUSPEND - set GUIGraphicsContext.State.SUSPENDING

Something tell MP to suspend :
[2015-11-20 06:54:33,110] [Log ] [MPMain ] [DEBUG] - Main: PBT_APMSUSPEND force restoring start screen to Bounds {X=0,Y=0,Width=1932,Height=1092}
[2015-11-20 06:54:33,112] [Log ] [MPMain ] [DEBUG] - Main: PBT_APMSUSPEND - set GUIGraphicsContext.State.SUSPENDING
[2015-11-20 06:54:33,114] [Log ] [MPMain ] [INFO ] - Main: Suspending operation
[2015-11-20 06:54:33,116] [Log ] [MPMain ] [DEBUG] - Main: PrepareSuspend - set GUIGraphicsContext.State.SUSPENDING
[2015-11-20 06:54:33,118] [Log ] [MPMain ] [INFO ] - TVHome.WndProc(): Windows is suspending
[2015-11-20 06:54:33,119] [Log ] [MPMain ] [DEBUG] - TVHome.OnSuspend


Look the time here :

[2015-11-20 06:54:32,935] [Log ] [TvClient-TvHome: HeartBeat transmitter thread] [INFO ] - TVHome: OnRemotingConnected, recovered from a disconnection
[2015-11-20 06:53:48,662] [Log ] [MPMain ] [INFO ] - Main: WM_POWERBROADCAST (PBT_APMRESUMEAUTOMATIC)
[2015-11-20 06:54:32,942] [Log ] [TvClient-TvHome: HeartBeat transmitter thread] [INFO ] - RemoteControl - Connected
[2015-11-20 06:54:32,943] [Log ] [MPMain ] [INFO ] - Main: PBT_APMRESUMEAUTOMATIC was already handled, skipping
[2015-11-20 06:53:48,659] [Log ] [MPMain ] [DEBUG] - Main: WM_DEVICECHANGE (Event: DBT_DEVICEREMOVECOMPLETE)
[2015-11-20 06:54:32,950] [Log ] [MPMain ] [DEBUG] - Main: Device type is DBT_DEVTYP_DEVICEINTERFACE - Name: Teredo Tunneling Pseudo-Interface
[2015-11-20 06:53:48,656] [Log ] [MPMain ] [INFO ] - TexturePacker: Loaded C:\ProgramData\Team MediaPortal\MediaPortal\Cache\TITANIUS\packedgfx26.png texture:2048x2048 miplevels:1
[2015-11-20 06:54:32,958] [Log ] [MPMain ] [INFO ] - TexturePacker: fontengine add texure:1989

06:54 then 06:53 and 06:54 and 06:53 what is wrong lol

Edit : ofc TvClient-TvHome is running in a separate thread but before that we have also such strange timing.

 

[HTPCSourcer]

Maybe you can try to wake up from WOL it seems in your last log there is few times where your PC waked up.

Correct, but remember that the time on the homescreen this morning was still 22:48, so the WOL wakeup at 3:30 didn't change anything and MP was already in this state then. But certainly no problem to do a WOL.

 

[Sebastiii]

Yep, the WOL resume the PC but not like when user is present, so MP staying like freezed so it can be normal, it's the last resume that is not correct, it should not act as suspending when resume lol.

It seems that left over code are executed async lol