Standalone - Client freezes randomly (1 Viewer)

[Mat Walker]

At seemingly random times of the day the Client freezes - not responding to any input. Process has to be killed and restarted.

During general use of MP (DefaultWide) the UI freezes, not responding to any Keyboard/Mouse input. Alt-Tab has to be used to get to desktop and then TaskMgr used to killed the process.

Noticed that the process sits on about 13-14% CPU and cycles between about 380Mb and 430Mb memory usage.

Logs grabbed after MP froze at about 17:55 (Activity after 17:55 is me logging in - 18:25 - from RDP (MP starts! I usually whip the startup out of the registry 'Run' to stop it) to get a log zip built for this report.

2 dual-tuner Hauppage and 1 dual tuner Compro tuners.. Quick machine; 16Gb 300Gb dedicated raptor recordedTV/Timeshift buffer disk.

 

[mm1352000]

Looks like you tried to start viewing Ten Digital at about that time. MP thinks it was timeshifting that channel successfully. If you were getting no reaction then I suspect codec issues, which brings me to...
Your TV codec preferences are not configured. Strange things like this can happen when codecs are not configured. So, please resolve that and see if the problem goes away:
http://wiki.team-mediaportal.com/1_...nfiguration/9_Codecs_and_Renderer/1_TV_Codecs

Note you may see the LAV codecs selected when you first go to that tab, but that's because they're defaults; it does not mean those settings are saved.

 

[Mat Walker]

mmn, you are worthy of every cent/penny of donation that comes your way

Thanks mmn, I'll dive into that and feed back to the forum the results/fix.

Is it the (Error) lines here that tell you about the CODEC issue;
[2014-07-09 17:55:42,690] [Log ] [MPMain ] [INFO ] - VMR9: added EVR Renderer to graph
[2014-07-09 17:55:42,690] [Error ] [MPMain ] [ERROR] - Failed filter: not found
[2014-07-09 17:55:42,691] [Error ] [MPMain ] [ERROR] - Failed filter: not found
[2014-07-09 17:55:42,692] [Log ] [MPMain ] [INFO ] - TSReaderPlayer: Render TsReader outputs

Then, 1 second later I see :-
[2014-07-09 17:55:43,643] [Log ] [97 ] [INFO ] - PlaneScene: video WxH : 720x576
[2014-07-09 17:55:43,644] [Log ] [97 ] [INFO ] - PlaneScene: screen WxH : 1844x1036

Is that a symptom as well (the screen is actually 1280x1080); IE. Due to the codec issue it is getting the screen resolution wrong?

 

[Mat Walker]

Well, I think I've ruled out a codec issue. Tried a software LAV and hardware DXVA (Native) modes... Got a lockup last night and again this morning.

If memory serves rightly both occured when I was moving between items in Recorded TV (no video playing)...

I've attached the logs from last night (Incident happened at 19:30 and had to kill MP process and restart). Nothing leaps out at me as obvious from the logs, but still early days on fully understanding what they are telling me

 

[mm1352000]

Is it the (Error) lines here that tell you about the CODEC issue;

Yes, those plus your config file and other lines in the TsReader log.

I've attached the logs from last night (Incident happened at 19:30 and had to kill MP process and restart).

If memory serves rightly both occured when I was moving between items in Recorded TV (no video playing)...

Log says you had just started playing a recording:
[2014-07-10 19:28:53,733] [Log ] [MPMain ] [INFO ] - PlayRecording:F:\Recorded TV\TEN Digital\MasterChef Australia\MasterChef Australia - 2014-07-08.ts - using rtsp mode:False

Do you have multiple displays connected, or are you disconnecting and reconnecting (or powering off and on) a TV, projector or receiver?
Just wondering if all the WM_DEVICECHANGE stuff I'm seeing is generated by RDP or something else.

 

[Mat Walker]

Yes, at 19:28 an episode of Master Chef started to be watched (sorry, yes, that was playing at the time of the incident - was not playing in the morning incident), then in the Recorded TV we were trying to select a different episode.

After I kill the process and restart I then log in to the machine on RDP to kick off the debug zip build - hence the RDP stuff.

That all said, and appreciating the RDPing in does muddy the waters, I'm now running on the standalone machine in debug mode (TITAN skin auto-selected)... Hopefully that will give a clearer picture (or... have the issue go away in which case my focus will move to the skin, DefaultWide, or its config).