Merged versions or series crashes emby server

[bruor 43]

I think I've found a bug in one of the updates within the last year.  I know for sure that this did not happen around 8 months ago (maybe slightly more).  Previous behavior is that the content versions would be stacked, and the local non .strm files would be preferred. 

My movie library consists of multiple folders.  Some contain media files, one contains .strm files. 

I had a series in my library as media files, and I have auto merge series across folders turned on.  

If I have a series downloaded, it loads in the UI fine.  If I add .strm files for the same show and it merges the episodes, I can't click on the episode from the continue watching feed or it will take me to a black screen in the client and crash the server.  I have to browse to the series selector, pick the episode from there and then I can watch it. 

Today I noticed 2 versions of a my in my feed, one .strm, one video file on my NAS.  I merged the versions, clicked on the movie in the "recently added" feed, and it crashed the server after showing me a blank screen in the client.  I tried browsing to it in the library, same result.  I tried frow the web client and I couldn't browse to it there either.  I ended up having to go to the library, folders, find the .strm version, remove it, quit and restart the client, and now I can open the movie without the server crashing. 

I can't attach logs right now without disrupting the family a lot more this evening.  Will try to reproduce the crash later with debug logging turned on. 

I specifically remember this use case not causing the server to crash. The .strm files were unreliable at one point so I downloaded a series to watch it without issues and emby was able to scan/merge and handle browsing/playback of the episodes without issue. 

 

[Luke 42081]

Hi there, let’s look at an example:

How to Report a Problem

Thanks.

[bruor 43]

I was able to pull the last log file from my server (63mb attachment)

I stood up a fresh installation and reproduced this by creating a library with 2 folders and a single movie.  An mkv in one and a .strm in another.  I turned on debug logging before capturing the log.  The only thing I did was click on the movie to be taken to it's page in the UI, then toggle between other screens and repeat. I didn't try to play it etc.  I tested from Chrome, the emby android app on my mobile, and the Android TV app on my Chromecast with Google TV. 

I was also able to verify that the server doesn't crash, it just becomes unresponsive because it consumes all ram and swap on the server, and fails to respond to connections.  The browser throws ERR_CONNECTION_REFUSED when trying to refresh the admin page, the apps just kick you to the main screen because they can't connect. 

The debug enabled server log on the fresh installation where I repro'd this is the 394kb file attached. 
 

embyserver-63837487959.txt embyserver-63837493615.txt

[bruor 43]

On the new instance, I have verified that deleting the .strm from disk outside of emby is not enough to resolve the memory leak.  I have to refresh the library so that the entry is removed and restart the server service.   When the library scan noticed the file was missing I saw a dip in memory usage, but then it quickly started increasing again until I restarted the service.  Now I am unable to cause the leak to happen again. 

The leak only seems to occur when you browse to a merged item in the library.  For instance, for the TV series, though I can't browse to the series on the Android TV app without triggering the leak, I can use the Android app on my phone to open the series object, select the episode, and use the cast button to play the episode I want on the emby app on my CCwGTV and no issues.

Edited December 7, 2023 by bruor

[bruor 43]

Actually, it looks like the leak was triggered again somehow automatically after the strm version of the movie was removed from the library.  I am unable to connect remotely to that machine now and will have to get someone on-site to power cycle it to regain access.  When able, I will see if removing and re-creating that library stops that issue. 

Please let me know if it is worth my time to try to re-create the issue with a tv series, and if you want any other logs once you've had a change to review what I've sent over so far. 

[Luke 42081]

OK yea this has been reported before and it is related to multi-version media when one or more of the versions is an strm file. It has been resolved in the upcoming 4.8 server release. Thanks.

[bruor 43]

Is it possible to move to the beta, and then switch to the stable once the initial stable release is made?

Edited December 7, 2023 by bruor

[Luke 42081]

14 hours ago, bruor said:

Is it possible to move to the beta, and then switch to the stable once the initial stable release is made?

Yes you can.