New update 1.32.8.7639 crashing randomly on synology nas

I’m on 1.40.1.8120 and have crashed multiple times within the same hour. Crashing about every day.

2 Likes

Hey Jason, Thank for the heads up. Glad I’m still on …7998. Hope the plex team resolves this asap.

I’m trying to understand how we went from a stable Plex Server application that could run for weeks or months (at least) without a crash, to one that will crash when things are playing, will crash when nothing at all is playing, will crash when everyone is asleep at 5 in the morning, will crash every day. I know this thread was started re: Synology. Are there specific ports that are suffering? I’ve been running Mac OS X Plex for many years and never had an issue until this one, which seems to be beyond the ability of the developers to make any progress on resolving.

Are Windows server users crashing, too? Why can’t we stabilize the app enough to run for 24 hours at the very least? (I’ve had Plex crash less than one hour after starting, btw). Can I supply logs to assist? I have MANY MANY MANY examples of Plex crashing, as you might expect. What would it take to prioritize solving a crashing issue beyond an issue, say, like this one which was part of the latest release notes:

(Extras) New preference for Cinema Trailers to always include English language trailers when account audio language is not set to English (PM-620)

Was this work a higher priority than resolving a crashing application? I’m just trying to understand. It’s been four months since this thread was opened. Is there even a bug tracker page for the issue? Not sure how you organize them.

Don’t mean to be a “complainer”, but I hope you can understand what my own priorities are, as a user: app runs. What higher priority should there be? If it can’t run, why are we using it?

Have you reverted to 1.40.0.7998 ? That has been incredibly stable since I installed mid February.

@jasonwoerner I totally agree with you. New features are always welcome, but unless the underlying program is stable they are worth nothing.
DVR users pay for a premium subscription, so ensuring our functionality is maintained should surely be factored into bug fix plans as well as the product roadmap.

@brenowitz I have also been running 1.40.0.7998 without issue for many weeks. I am reluctant to update without evidence that the cause of the crashes has been diagnosed and rectified. Being stuck on 1.40.0.7998 means I am potentially missing out on new features and other fixes.

I hope those in the Plex organisation who manage product maintenance and development recognise the frustration of its customers and direct resources to resolve the problems.

No need for FOMO. Read the release notes. Unless there is a compelling reason to update, do not do so.

Unless there is something Synology specific, you might be able to load PMS on another system (PC, Mac, etc.) to test any fixes/new features/etc.

That’s a fair point @FordGuy61, but I am not convinced the release notes are comprehensive.
Curiously it seems there are sometimes consecutive releases with the same notes. (Though maybe this is a beta followed by a public release).

I’d like to chime in on this with crashing issues on docker, see this post:

I see that PMS 1.40.2.8395 is now available. Before I install it (to replace 1.40.0.7998 which has been running without problems for over 2 months), has anyone who uses the PVR functionality and previously experienced random crashes tried this new version?

@ChuckPa It’s been nearly 6 months since this was raised (and appears to be affecting more users than previously thought). Can we have an update on this?

Hi @olinash and @ChuckPa I am still running 1.40.0.7998 which is stable for the PVR functions.
I’d like to upgrade to the latest version but don’t know if I’d be able to revert in case of problems, given there have been major database changes.
Who can advise?

I, unfortunately, have no DVR capability here with which to test anything. (3 years)
I don’t know either way how well it does / doesn’t work.

Regarding the DB, the major change came with 1.40. Once above 1.40, you’re much more “DB-stable”.

Can you check whether there have been any updates on bug report #14691? Has this been marked as resolved internally?

Thanks,

I could find it immediately.

It was looked at but the DMP file was a zip of the logs.
It’s sitting in blocked status (I wasn’t notified)

Can you

  1. Turn off crash report uploading
  2. Recapture the DMP
  3. Add the DMP to the ZIP of the logs so it’s all in one file?

Happy to do this but can you provide a copy of version 1.32.7.7621 (this is the version we downgraded to as a workaround - which we’ll need to do again whilst we wait for this to be fixed).

The update showing as available now is 1.40.2.8395. Can you confirm that we’ll have no issues trying to rollback to 1.32.7.7621? If this isn’t possible can you provide the next version up from 1.32.7.7621 so we can replicate the fault, then rollback to a working version whilst a fix is developed?

Also, to ensure we capture everything you need, could you outline the exact steps the dev team want to capture the DMP?

which binary? debian or redhat ?

We’re running a Synology DS923+ so the AMD 64bit version (for DSM7)

@olinash

Check your PM.

Thanks @ChuckPa, have just replied

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.