Tvheadend

Have you tried adding HMF_DBL to switch(f->hmf_type) to see what happens then? If not, could you please give that a try to see if that is fixing the issue or if an invalid time is then sent out over HTSP.

Mmm, i don't know as its the same bug. For me restarting TVH is not a problem, even after installing new build it crashes. Duration entry is present in file, but seems to be ok.

Restarting after the recording was meant here, I think that is exactly what you see. What is the duration entry in the file that causes the crash for you? There must be one (or multiple) files that cause the crash while they are there, when moved away tvheadend should run normally.

I recorded a show yesterday, after that i restarted tvh and its ok. Did a restart just before 1 Minute to check that, connected with Kodi, no crash....
As i said, at least with every update (equal which build i install) i'm not able to use Kodi till i delete all logfiles. No prblem for first, as i'm on buster no and there is no new buster build since long time ;-)

Because the new recording wasn't long enough to be considered a HMF_DBL (double). The recording that is mentioned above has a duration of 1040792 hours (so it's most likely an incorrect entry). I am sure that you have the same issue, an incorrect duration entry that just breaks everything. There is no way to figure out how it ended up there now, but I am pretty sure that there are some more memory corruptions somewhere in the code that haven't been found yet.

Mmm...but i remember that i backuped my older logs and copied just one of them back after updating the app just to figure out there was an corrupt file. After that i restarted the server and boom, Kodi, crash... Did that with some other one after the other, but no luck. I had to delete them all, my autorecordings are set after each try, that works.
At least i did a complete new setup, scanned all channels, created all my recording profiles, but that didnt help. If i find time maybe i will try on one of my other devices and see if i can reproduce the crash.
Btw, strange thing.

Checked my dvr logs again, all recorded have same "duration": 1800," value inside, planned recordings don't have this value....

You need to check that when you have the crashes. It could also be any other field there that is corrupted (like starttime or endtime).

I also have this problem, recording is simply unusable at the moment. I run linuxserver/tvheadend docker image with version 4.3.-1880-
I can share recording files from log directory if wanted.

looking at the values start and stop is correct (both values, also with start_extra and stop_extra).
duration is 3600 what means 60 minutes? and is wrong as duration is 2h plus start_extra and stop_extra.

First of all a stacktrace is needed to verify that it's indeed the same issue.

Hi, here I attach a coredump and a gdb.txt, I don't know if it's ok, but I can try to get the files again if not.

https://drive.google.com/drive/folders/1ejp1yYAqUcRsuYe1hkwSdkP8UsdbOCZA?usp=sharing

https://tvheadend.org/projects/tvheadend/wiki/Debugging#Incorrect-not-useable-crash-reports

Thanks, I think I see the issue now: The JSON Parser is not "designed" for int64_t but only for long, whenever the range of a long is exceeded it falls back to a double. A double is not defined in the binary protocol (which is "unexpected" and causes an abort then), so we need to adapt the json parser for int64_t and remove the long (it's no longer used then). If nobody else does it I might come up with a patch during the next few days.

My first attempt to fix this is at the Fix-Long Branch. It's entirely untested so I don't know if it will compile or not. If someone wants to give it a try please go ahead and report back, if not I will need to test it myself when I find some time.

It compiled after I made a small change (which I've submitted a PR for). The crash when Kodi connects no longer occurs.

Confirmed, compiled and installed it and no crash