Deleting an entity with revisions and file/image field does not release file usage of non-default revisions, causing files to linger

Patch #119 can't be applied to Drupal 9.5.10

I think we should postponed this on 🌱 Dealing with unexpected file deletion due to incorrect file usage Active

@steinmb This is one of the issues noted in the table in 🌱 Dealing with unexpected file deletion due to incorrect file usage Active . And I don't know of a reason work on this cannot proceed in parallel to the others there?

As the notes column there says regarding this issue: "No data loss, but irrepairable, therefore still critical."

file_usage does not seem to get touched when a filefield gets deleted.
So we can not even find those files anymore that had been referenced (= used) by the deleted field. At least not in bulk.
All files still keep value "1" in column "status" .
At least this value should have changed after deletion of the field.
Am I wrong?

This should really be postponed on 🌱 Add a reliable entity-usage system to core Active , the file_usage system is broken beyond repair, there is no way to rebuild file usage, so as soon as it's off by one or more, it's like that forever.

I posted a potential solution/workaround in 🐛 File not marked temporary and usage not updated if only used in past revisions when node is deleted Active

I also disagree that this should be postponed. Leaving it as-is will continue to create incorrect file usage data any time someone deletes content, which will only make their problems worse. The solution I shared in the previous comment isn't that difficult or complicated.