How does this work with the recently added attachment/subtitle cleanup? Does that not rely on the db having the old paths? (I'm not sure and I can't figure out how it works by looking at the code (not even sure i was looking at the right spot))

Give the error, it seems to me the old attachments have either already be cleared from disk, or not yet. (I think the former, so removing them from the DB is fine?)

How does this work with the recently added attachment/subtitle cleanup? Does that not rely on the db having the old paths? (I'm not sure and I can't figure out how it works by looking at the code (not even sure i was looking at the right spot))

Give the error, it seems to me the old attachments have either already be cleared from disk, or not yet. (I think the former, so removing them from the DB is fine?)

[INF] [79] MediaBrowser.Providers.Movies.MovieMetadataService: File changed, pruning extracted data: /path/to/attachments

When Jellyfin detects that the video file has changed, or the user manually triggers a media library scan, the old attachment will be deleted, so the scheduled task should not have a chance to delete the attachment in this case.

In this case the attachment had been deleted, but the database still had the old information, which led to the failure of real-time extraction of attachment fonts and web rendering of subtitles. This fixes that mismatch.

最新版本jellyfin ，pve lxc docker部署，扫描媒体库会出现内存泄漏的问题。