Project

General

Profile

Forums » Kodi (XBMC) as frontend »

Continuity errors causing Kodi to become unresponsive

Added by Robert Cameron about 8 years ago

I running 4.1, and have noticed a problem with recent builds. Previously I was running 4.1.r2199~ga88ba9d and had no real problems. However, when I upgraded to 4.1.r2216~gfd7806a I started having problems:

When watching a stream and a continuity error was encoutered, previously the stream would pause for a moment and then when the error was recovered from, the video would speed up to resync with the audio. But, when running on r2216~gfd7806a, occasionally instead of playback resuming as it had previously, once the error was recovered from and the audio resumed, the video would either remain frozen or go completely black. This wouldn't be so much of a problem if I could stop the stream, but when this happens Kodi becomes unresponsive. The audio continues to play, but otherwise I cannot interact with the machine; I either have to force poweroff the machine or SSH in to restart my kodi.service.

I believe this is tied to commit e666e0f, which is noted as: tsfix: remove mpeg2video recover pts - let's see what happens.

Has anyone else had similar problems? Does anyone have any ideas on how to track this down? The hassle with troubleshooting this is that when it occurs I am watching TV and don't really want to drop everything to make copies of log files and trace through exactly what happened, so I haven't gotten around to doing that yet; instead I just downgraded my installation back to r2199.

If this is a problem/bug and not just something wrong with my setup, I'll happily open a ticket. I suppose I could also just revert that one commit in my local copy and try running it without it in ...


Replies (2)

RE: Continuity errors causing Kodi to become unresponsive - Added by Mark Clarkstone about 8 years ago

Robert Cameron wrote:

I running 4.1, and have noticed a problem with recent builds. Previously I was running 4.1.r2199~ga88ba9d and had no real problems. However, when I upgraded to 4.1.r2216~gfd7806a I started having problems:

When watching a stream and a continuity error was encoutered, previously the stream would pause for a moment and then when the error was recovered from, the video would speed up to resync with the audio. But, when running on r2216~gfd7806a, occasionally instead of playback resuming as it had previously, once the error was recovered from and the audio resumed, the video would either remain frozen or go completely black. This wouldn't be so much of a problem if I could stop the stream, but when this happens Kodi becomes unresponsive. The audio continues to play, but otherwise I cannot interact with the machine; I either have to force poweroff the machine or SSH in to restart my kodi.service.

I believe this is tied to commit e666e0f, which is noted as: tsfix: remove mpeg2video recover pts - let's see what happens.

Has anyone else had similar problems? Does anyone have any ideas on how to track this down? The hassle with troubleshooting this is that when it occurs I am watching TV and don't really want to drop everything to make copies of log files and trace through exactly what happened, so I haven't gotten around to doing that yet; instead I just downgraded my installation back to r2199.

If this is a problem/bug and not just something wrong with my setup, I'll happily open a ticket. I suppose I could also just revert that one commit in my local copy and try running it without it in ...

You can still revert that commit, but please do open a ticket (kind of a this effects me thing), the discussion about it occurred on IRC you can view that here: http://colabti.org/irclogger/irclogger_log/hts?date=2016-08-24#l70

RE: Continuity errors causing Kodi to become unresponsive - Added by Robert Cameron about 8 years ago

Thanks for the link to the IRC logs. When I have more time later I'll sit down and review everything.

Tracking down the times and logs for everything really shouldn't be that much of a hassle: I can browse the Kodi logs to find out when it was restarted to get reference points, and then look those times up in the TVH logs. I'm not sure what level of logging I have enabled in Kodi, so I am uncertain if they will provide much information.

I'll also read through the IRC logs to see what exactly is being discussed: that way I'll be able to open an issue ticket with some concrete information instead of just random imprecise observations.

    (1-2/2)