I know this isn’t the solution you likely want, but depending on how many recurring recordings you have set up you can remove those and it should allow the DVR to continue working, at least it did for me.
I only had one set up, so it wasn’t a big deal to remove it until this is resolved. But you will have to remove them in a stable version before you can run the new one because when it gets to the DVR setup step to reschedule existing ones is when it appears to blow up the server. Single scheduled recordings are ok, recurring is what appears to be broken. But perhaps that’s just my specific use case, and still something larger at play.
There is likely a way since the entries must be stored in the database somewhere, but I’m afraid I don’t know the structure well enough and sqlite isn’t the most friendly database software. My best suggestion would be to manually note all your ongoing recordings, and recreate it later. But that’s far from ideal.
Even with doing all that you will need to keep manually scheduling the individual recordings until this is resolved, so if you have a lot this may not be the right solution vs staying on the older version until this is solved.
Running 1.23.2.4656, and since this update mine is crashing as well (running on Synology). Can confirm that deleting the DVR fixes the issue, but it will reappear after adding the EPG.
Can someone please get me a DMP file from the “Crash Reports” directory?
(Turn off “Upload Crash Reports to Plex” to keep the file locally)
From that DMP, I can find out where it’s crashing and give the information to Engineering quicker than waiting for the reports to be printed later this month.