Media Portal freezes on wake (4 Viewers)

[Sebastiii]

Yep it seems that 0-1-2....-9 didn't work (at least for me on remote) but keyboard or num pad is ok. @Stéphane Lenclud any idea ? i have try to look at MP config section and i can even add it too, so i miss MCE lol

 

[HTPCSourcer]

First test results:

• HTPC1 sent manually into Standby (note that normally it is woken up by the server for the nightly backup around 4am - I did not check logs)
• Wake-up brought the known smaller MP homescreen, which switched to full screen after a few seconds. The task bar remained visible and the time on homescreen was the one from yesterday evening when I had switched off.
• After some longer time (maybe 30 s) the task bar disappeared, however, MP was unreactive. I swirrched back and forth with Alt-Tab without any visible effect.
• I also pressed keys and clicked on the MP home screen without any immediate reaction
• Suddenly TV started in full screen.
  • However, something is then wrong with MP. The upper menu bar (Titanius), which I use to control TV/Video with the mouse is greyed-out and not usable.
  • Back/ESC brings up the TV menu (with TV on, TV programme, recordings, etc.). Switching off TV in this screen stops Live TV but a still picture remains visible in the little window.

At this time I killed MP from the task bar and collected logs.

 

[mm1352000]

@HTPCSourcer
There are quite a few exceptions from the WorldWeather plugin. I don't know if they are having any effect on what you see.
There are also a couple of exceptions relating to the GUIVideoOverlay, which may be connected to the "upper menu bar" issues you described.
The most suspicious thing of all are these entries in the middle of the resume process:
[2015-11-17 07:39:26,452] [Log ] [MPMain ] [INFO ] - Main: Suspending operation
[2015-11-17 07:39:26,455] [Log ] [MPMain ] [INFO ] - TVHome.WndProc(): Windows is suspending

Very strange!
Unfortunately the log level is info rather than debug. This makes it very hard to follow what was happening.
Sorry to ask you to do the same thing again, but debug level logs are really needed for problems like this.
If you're going to use the watchdog with option 3, please manually set the log level to debug and post fresh log files after reproducing the problem again.

[edit: Actually in some places it seems like info level log lines are missing. This is also very strange, and another reason why I'd need another set of log files. ]

[edit 2: It seems like the above entries are associated with the suspend notification that was received after the backup completed:
[2015-11-17 04:20:50,397] [Log ] [MPMain ] [INFO ] - Main: WM_POWERBROADCAST (PBT_APMSUSPEND)

Note the 2h 40m gap. Something really funky is happening there!]

 

[HTPCSourcer]

Unfortunately the log level is info rather than debug.

Oh sh...! I had changed this before yesterday for some other reason and forgot to put it back to Debug. Next logs tomorrow morning

 

[HTPCSourcer]

This morning I found MP to have crashed ("MP has stopped working", so the value of the attached logs might be limited.

EDIT: The logs are useless. I had manually sent the PC into standby at 23:07, yet something must have gone wrong then. So we go for another round.

I am also surprised to see the message that Client and Server don't have the same version. Seb, did I pull the correct download from Jira (1.12.100-94 gcf519d4)?

 

[mm1352000]

This morning I found MP to have crashed ("MP has stopped working", so the value of the attached logs might be limited.

EDIT: The logs are useless. I had manually sent the PC into standby at 23:07, yet something must have gone wrong then. So we go for another round.

Yes, this time it appears to be MP-TVSeries plugin causing a crash during the standby/hibernate process:
[collapse]
"17.11.2015 23:08:18";".NET Runtime";"(0)";"Error";"Anwendung: MediaPortal.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.AccessViolationException
Stapel:
bei SQLite.NET.SQLiteClient.sqlite3_prepare16(IntPtr, System.String, Int32, IntPtr ByRef, IntPtr ByRef)
bei SQLite.NET.SQLiteClient.Execute(System.String)
bei WindowPlugins.GUITVSeries.DBTVSeries.Execute(System.String)
bei WindowPlugins.GUITVSeries.DBTable.ReadPrimary(WindowPlugins.GUITVSeries.DBValue)
bei WindowPlugins.GUITVSeries.DBSeason..ctor(Int32, Int32)
bei WindowPlugins.GUITVSeries.OnlineParsing.GetEpisodes(Boolean, Boolean)
bei WindowPlugins.GUITVSeries.OnlineParsing.worker_DoWork(System.Object, System.ComponentModel.DoWorkEventArgs)
bei System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs)
bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(System.Object)
bei System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr, System.Object[], System.Object, System.Object[] ByRef)
bei System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
bei System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object)
bei System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
bei System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
bei System.Threading.ThreadPoolWorkQueue.Dispatch()
bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
";"1026"
"17.11.2015 23:08:23";"LightsOutClient";"(0)";"Information";"Lights-Out ClientService Power event: ResumeAutomatic";"103"
"17.11.2015 23:08:23";"Application Error";"Anwendungsabsturzereignisse";"Error";"Name der fehlerhaften Anwendung: MediaPortal.exe, Version: 1.12.100.94, Zeitstempel: 0x56458371 Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.10240.16430, Zeitstempel: 0x55c599e1 Ausnahmecode: 0xc0000005 Fehleroffset: 0x00055635 ID des fehlerhaften Prozesses: 0xde4 Startzeit der fehlerhaften Anwendung: 0x01d121846351a586 Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll Berichtskennung: 1296eb7e-8a5d-497a-9c2f-5ce9a974b716 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: ";"1000"
"17.11.2015 23:08:29";"Windows Error Reporting";"(0)";"Information";"Fehlerbucket 107751538802, Typ 1 Ereignisname: APPCRASH Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: MediaPortal.exe P2: 1.12.100.94 P3: 56458371 P4: ntdll.dll P5: 10.0.10240.16430 P6: 55c599e1 P7: c0000005 P8: 00055635 P9: P10: Angefügte Dateien: Diese Dateien befinden sich möglicherweise hier: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_[/collapse]

I might guess this is either due to the location of the database or that MP-TVSeries is not fully thread safe (eg. able to cancel lookup cleanly if standby notification is received).

I am also surprised to see the message that Client and Server don't have the same version. Seb, did I pull the correct download from Jira (1.12.100-94 gcf519d4)?

The client version is based on a commit somewhere between MP 1.12 final and 1.13 PR. Since your TV Server is running 1.12 and you only ran the update on the client, it's no surprise to me that the versions don't match. It's allright though - the versions should be close enough to be compatible.

 

[Sebastiii]

Hi i'm tagging @ltfearme if he has an idea about the threadsafe (but yep it can be related to location of database)

 

[Sebastiii]

About TvServer / TvPlugin version, the TVServer is 1.13 pre release (1.12.100) but this installer is created with version number, so like mm said, there is no diff about the client side, so it's ok

 

[regeszter]

there is no diff about the client side

There was code change in server and client side too. But the 1.12 is compatible with 1.13 of course.

 

[HTPCSourcer]

Hello,

resume this morning had MP showing ok, except for a FanArt Handler dialogue that the database could not be created.

Except for the database errors MP appeared to not have crashed, although there was somekind of focus problem. Initially MP was unreactive and I had to swicth between windows with Alt-Tab back and forth first before I was able to OK the error dialogue and get into MP. I then was again able to navigate on the home screen.

With respect to the datbasases being remote, the ideal solution would be to have MP wait until the server / remote share is accessible.