Latest version of Emby - Random lockups - Connection Timeout to https://api4.thetvdb.com

[Luke 43166]

No but there’s no reason to do that.

[vaise 344]

53 minutes ago, Luke said:

No but there’s no reason to do that.

I am just out of ideas on what to try here.  Plugins and external systems all gone.

The system has gone from something I don't think about to something that needs regular restarts and I have no known reason for that.  It all started with the new release, so I just want to roll that back to see if it is stable again for a week for example.  If it is stable, then it is the new release that has an issue with my config, and I am running out of time before I leave my system for 7 weeks so need it stable before then.

So can I do this  and not break anything ?

But then, I don't know what version I was on now - what was the latest release before this new version ?

Edited 3 hours ago by vaise

[Luke 43166]

From what version number to what version number?

[vaise 344]

I am now on Version 4.10.0.40.

I don't know what I was on last month for example, but it was the 'latest' at the time.

[vaise 344]

AI thinks this was 4.9.5.0 a month ago ?  but it also was worried about database changes.......  AI says that was the stable 'latest' version as at mid May 2026.

Today's straws I have clutched at - 

- deleted emby cache file and restarted container to rebuild

- changed container to 16GB RAM instead of 8GB - but note I had tried 12GB when this first happened - hence why I think its a leak.

- Removed subtitle and font extraction on the fly

- Stopped frigate container from using the GPU

- Stopped Calibre container from using the GPU (its all emby now).

- Confirmed enable throttling is set in emby

- Confirmed transcoding is to disk

- Reviewed all transcoding remote clients - Contacted them to upgrade or I will turn off their transcode capability.

Note - I rarely see transcoding, I tune my system to be direct play - I have a few non Emby for Android holdouts I am rounding out - as they seem to transcode.

 

[Luke 43166]

Well your original issue was tvdb timeouts. I wonder if they're just throttling you.

[vaise 344]

10 minutes ago, Luke said:

Well your original issue was tvdb timeouts. I wonder if they're just throttling you.

I can't change the title now - should I open a new post with the out of memory issues ?

The first failure - I never check logs, just restarted.  The second was what I posted this initially, and the logs.

Since then its all killed with no logs.  

Related? I don't know.