Mediaportal 1.3.0 stopped unexpectedly (1 Viewer)

[adrian5800]

Hi
I have been experiencing random crashes in MP recently.
Can someone have a look at my logs and give me a clue as to the cause. I can't see anything obvious that could cause this. I don't want to do a fresh install if I can help it.


Many Thanks

Adrian

 

[jehe]

Hi adrian,

Please disable your plugins, you can do this by running mediaportal in debug mode.
http://wiki.team-mediaportal.com/1_..._and_Bug_Reports/WatchDog?highlight=watch+dog

Can you give some more info when these crashes occur?

 

[mm1352000]

I agree with Jean

The last log entry at roughly the time of the crash at ~8:30pm on the 27th is related to MovingPictures.
Having said that...
I'd have expected to see more entries as playback stopped... so maybe that TsReader crash is happening here @Owlsroost ?

mm

 

[Owlsroost]

Do these crashes only happen when stopping TV/recordings, or does it happen with other video files as well ?

If you want to try it, the latest 'dev release' TsReader.ax (v73_dev) is here - https://forum.team-mediaportal.com/threads/experimental-tsreader-development.102693/#post-811296 - but I've also attached a even newer version below (v74_dev) in case v73_dev doesn't fix it (assuming it's a TsReader.ax problem in anyway, which is hard to tell from the logs).

 

[adrian5800]

Thanks for the replies, last night I updated all the plugins and MP ran all day without a problem until this evening. This was watching DVB-T tv (which was when it would crash intermittently).
I restarted MP in debug mode with default skin and no plugins as you suggested Jean. So far no crashes but I will update and post logs when/if it does.
MM - I have had MovingPictures data base corruption in the past that required a database wipe and rebuild. I would like to be sure of the cause before I go slashing and burning again ;-)

Edit-

Do these crashes only happen when stopping TV/recordings, or does it happen with other video files as well ?

Only when watching live DVB-T

I won't try TsReader changes until I'm sure of the cause thanks.

Cheers

Adrian

 

[adrian5800]

Here you go guys. Left MP running all night in debug mode and it crashed watching DVB-T.
Logs attached

Cheers

 

[mm1352000]

"30/05/2013 4:29:32 AM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 3554844371, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.3.0.0 P3: 512d0eeb P4: MSVCR100.dll P5: 10.0.40219.1 P6: 4d5f0c22 P7: c0000005 P8: 00001ed7 P9: P10: Attached files: C:\Users\adrian\AppData\Local\Temp\WER1262.tmp.WERInternalMetadata.xml C:\Users\adrian\AppData\Local\Temp\WER2F94.tmp.mdmp These files may be available here: C:\Users\adrian\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_a5b4fa391cc425114b4c724670b7ede0cb75c56d_019581fb Analysis symbol: Rechecking for solution: 0 Report Id: a0360dd8-c869-11e2-955c-00012e472223 Report Status: 9";"1001"

Some C++ component is crashing on the MP side... however things don't look entirely "rosy" on the TV Server TsWriter side either.
Lots of failed to create/reopen file.
Then we have continuity errors starting probably due to the HDD working hard (out of space?).
Finally we start to see PCR forward jumps.
Maybe the PC rolled over... but that would be a bit early based on the TsWriter check at start of timeshifting.
Was TV Server still "happily" timeshifting when you awoke, or had it also crashed? I ask because the PowerScheduler entries stop abruptly at the time of the MP crash. That could just be due to MP crashing, but wouldn't want to second-guess...

 

[adrian5800]

Some C++ component is crashing on the MP side... however things don't look entirely "rosy" on the TV Server TsWriter side either.
Lots of failed to create/reopen file.
Then we have continuity errors starting probably due to the HDD working hard (out of space?).

C drive isn't exactly out of space 28GB free of 128GB, though I notice there are 40GB+ of recent tv recordings in C:\ProgramData\Team MediaPortal\MediaPortal TV Server\recordings. This I don't understand because I have set my folders for tv recording and timeshifting to D:\Recorded TV and D:\Timeshifting (a 2TB external drive) initially when I first installed MP over a year ago and they are still set this way in Tv server config (see attached doc). MP must have been recording to the C drive folder instead of the D drive because the D drive recordings are dated up to March this year and the C drive ones are from March to present. Could this be an issue (aside from the wrong location being used)?

Finally we start to see PCR forward jumps.
Maybe the PC rolled over... but that would be a bit early based on the TsWriter check at start of timeshifting.

When you say "rolled over" do you mean rebooted? The pc is set to resume on lost power.

Was TV Server still "happily" timeshifting when you awoke, or had it also crashed? I ask because the PowerScheduler entries stop abruptly at the time of the MP crash. That could just be due to MP crashing, but wouldn't want to second-guess...

I can't tell if the tv server was still running as the client side of MP crashed. Is there another way to check?

Cheers

 

[mm1352000]

C drive isn't exactly out of space 28GB free of 128GB...

Well, depending on your timeshift settings that space could potentially be totally used as back-buffer if you leave TV on for long periods of time.
This might well explain what happened last night, though in general only you know if it takes a long time for crashes to occur.

...though I notice there are 40GB+ of recent tv recordings in C:\ProgramData\Team MediaPortal\MediaPortal TV Server\recordings. This I don't understand because I have set my folders for tv recording and timeshifting to D:\Recorded TV and D:\Timeshifting (a 2TB external drive) initially when I first installed MP over a year ago and they are still set this way in Tv server config (see attached doc).

Recording folders are set on a per-tuner basis.
Your pic only shows the recording folder for the built-in DVB-IP tuner. More important is the recording folder setting for the tuners that would have made those recordings.
It is extremely unlikely for this to be a bug/issue as such a problem would have been reported and fixed very quickly.
I suspect a simple mistake in configuration here. It is easy to do.

Finally we start to see PCR forward jumps.

Maybe the PC rolled over... but that would be a bit early based on the TsWriter check at start of timeshifting.

When you say "rolled over" do you mean rebooted? The pc is set to resume on lost power.

This was a technical comment that was directed more at Owlsroost (the resident TsReader maestro). Don't worry about it.

Was TV Server still "happily" timeshifting when you awoke, or had it also crashed? I ask because the PowerScheduler entries stop abruptly at the time of the MP crash. That could just be due to MP crashing, but wouldn't want to second-guess...

I can't tell if the tv server was still running as the client side of MP crashed. Is there another way to check?

The server and client are entirely separate processes, so MP client can crash without TV Server crashing (and vice-versa).
You can check the TV Server status in many different ways.
The easiest is probably to open TV Server configuration. If you get prompted to start the TV service when you do this then you know that the TV Server was not running (ie. it probably crashed).

 

[adrian5800]

Well, depending on your timeshift settings that space could potentially be totally used as back-buffer if you leave TV on for long periods of time.
This might well explain what happened last night, though in general only you know if it takes a long time for crashes to occur.

I'd say that is exactly what has happened.
Could we have found the problem?

Recording folders are set on a per-tuner basis.
Your pic only shows the recording folder for the built-in DVB-IP tuner. More important is the recording folder setting for the tuners that would have made those recordings.
I suspect a simple mistake in configuration here. It is easy to do.

Spot on-the tuners were set to C: drive. Though it is strange as they were originally set to D: - there are months of recordings in D:

You can check the TV Server status in many different ways.
The easiest is probably to open TV Server configuration. If you get prompted to start the TV service when you do this then you know that the TV Server was not running (ie. it probably crashed).

When I opened tv server config it didn't prompt to restart the server..



Now I have fixed up my mistakes in the config, I'll run it and see if it's now fixed.
Thanks for your help

Cheers


Adrian