1.14.0 MP crash after fast rewind live tv (1 Viewer)

[RicoHTPC]

Hello guys

I discovered a bug when watching live tv and using fast rewind.
I can not reproduce this on my bedroom system but on my living room client this is how to:
-start live tv
-pause it
-rewind
-press play
MP will the crash and show a flickering screen.
Both clients are running unc.

Grateful for every bit of help.


Cheers

Rico

Edit: In the logs the event was at 21:09

 

[mm1352000]

Hello Rico

First, thanks for the report.

I don't see any evidence of a crash in the log files. When a crash occurs, I'd expect to find a record in the Windows application event log. In your case there is no such record. The MP error log is also empty. So, please can you describe what you mean by "crash".

What I do see is the following:
1. You start MP.
2. You start viewing RTL Television successfully.
[2016-02-03 21:07:32,932] [Log ] [MPMain ] [INFO ] - TVHome.ViewChannelAndCheck(): View channel=RTL Television
[2016-02-03 21:07:34,869] [Log ] [MPMain ] [INFO ] - succeededucceeded TvControl.VirtualCard
...
[2016-02-03 21:07:36,197] [Log ] [MPMain ] [WARN ] - tvhome:startplay. Phase 2 - 1304 ms - Done starting g_Player.Play()

3. You attempt to rewind at x2, x4, x8, x16 and x32 speed.
[2016-02-03 21:08:59,631] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate to:-2 80004005
[2016-02-03 21:08:59,705] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate - fast seeking is not supported, falling back to normal seeking
[2016-02-03 21:09:01,371] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate to:-4 80004005
[2016-02-03 21:09:01,497] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate - fast seeking is not supported, falling back to normal seeking
[2016-02-03 21:09:06,124] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate to:-8 80004005
[2016-02-03 21:09:06,168] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate - fast seeking is not supported, falling back to normal seeking
[2016-02-03 21:09:08,150] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate to:-16 80004005
[2016-02-03 21:09:08,226] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate - fast seeking is not supported, falling back to normal seeking
[2016-02-03 21:09:09,620] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate to:-32 80004005
[2016-02-03 21:09:09,660] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate - fast seeking is not supported, falling back to normal seeking

4. You stop rewinding, stop TV and close MP.
[2016-02-03 21:09:10,163] [Log ] [MPMain ] [INFO ] - VideoPlayeretRate to:1 0
...
[2016-02-03 21:09:18,498] [Log ] [MPMain ] [INFO ] - g_Player.OnStopped()
...
[2016-02-03 21:09:40,090] [Log ] [MPMain ] [INFO ] - Main: Exiting


So again, I don't see any evidence of a crash. Despite what you saw, you appear to be able to stop the player and close MP as normal.

Perhaps whatever you're seeing ("flickering screen" etc.) could be related to the "fast seeking is not supported" messages. My understanding is that those messages/limitations are due to your choice of codecs. Without log files from the second client, I can only guess that the behaviour differences you're seeing are most likely to be caused by differences in codec configuration. In other words: maybe you should try different codecs if you want to see different behaviour.

Regards,
mm

 

[RicoHTPC]

@mm1352000: thanks for the fast reply
Good news first: I tried a different codec setting and it seems to work now.
At first I didn't expect this to be a factor because the other client had the same setting but then that one
has different hardware so this does make a difference.

One word to the crash: the screen was flickering between to pictures and I wasn't able to exit this screen although I had stopped tv.
MP seemed to react in the background from what I have seen on my secondary screen but regarding to the primary screen it was
stuck on the flickering tv screen. The only way out of this was to restart mp.

 

[mm1352000]

Good news first: I tried a different codec setting and it seems to work now.

Great.

...but then that one has different hardware so this does make a difference.

Yes, true.

One word to the crash...

Okay. This is not what I would describe as a "crash". When I read "crash" I think of MP closing suddenly and uncontrollably (without close/exit request). Still, what you saw is obviously some kind of problem. The question I ask is: was it something to do with MP? I don't have a certain answer to that question. My guess is that it was something to do with the GPU, and perhaps caused by the attempt to rewind leading to either MP, TsReader or codec asking the GPU to do something it isn't capable of doing. I'm not sure how to debug the situation further.

Is this something you're hoping that somebody will look into?
...or should I set the thread status to "no bug"?
...or...?

 

[RicoHTPC]

Sorry for the late reply.
I don't want to create work when this is actually no mp related problem.
I just wanted to point out that there may be something that is caused by mp but if this is not reproducible on other systems
this doesn't seem to be the case.
If changing the codec is a permamently working solution I am happy with that.

Cheers

Rico