Bug #5067

HTSP channelAdd method returns wrong values

Added by Arnaud Grasset 14 days ago. Updated 10 days ago.

Status:FixedStart date:2018-04-09
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:HTSP
Target version:-
Found in version:4.3-1218~ga441514ba Affected Versions:

Description

When tvheadend sends back the initial data dump after a enableAsyncMetadata message is sent, the values returned in the "channelAdd" message are wrong:

Doc says:
eventId u32 optional ID of the current event on this channel.
nextEventId u32 optional ID of the next event on the channel.

But eventId and nextEventId are always the same event until the next restart of the tvheadend service. So if I don't restart tvheadend daily, the channelAdd method returns the eventId of an event that is one week/one month (or more) old.

Associated revisions

Revision 518d57be
Added by Jaroslav Kysela 10 days ago

epg: fix the running check in _epg_channel_timer_callback(), fixes #5067

History

#1 Updated by Jaroslav Kysela 14 days ago

It would mean that the old EPG events are not freed. I suggest you to check the traces to analyze the issue: --trace epg.

#2 Updated by Arnaud Grasset 11 days ago

You are right. The real problem is that EPG events do not get deleted.

My tests:
- I compiled the last 4.2 version from git with debug enabled. Everything worked perfectly, logs showed old EPG events being destoyed as soon as they expired.
- I compiled the git master (4.3) with debug enabled and installed it. EPG events were not deleted and debug and trace showed nothing. There was no error, just nothing happened when an EPG event expired.

#3 Updated by Arnaud Grasset 11 days ago

Finally I have still the same problem with 4.2 version..

Solved it by disabling over-the-air EPG on my adapters.

#4 Updated by Jaroslav Kysela 10 days ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Also available in: Atom PDF