[Bug]: Input image held open by COM surrogate

[vecuccio]

Checklist

• The issue has not been resolved by following the troubleshooting guide
• The issue exists on a clean installation of Fooocus
• The issue exists in the current version of Fooocus
• The issue has not been reported before recently
• The issue has been reported before but has not been fixed yet

What happened?

I think this has been caused by an update to Windows 10x64, because this never used to happen before.
Sometimes, (maybe 1 in 4 times) when you are inpainting an image, and save the outputted file overwriting the file you used as the input image, you think it has overwritten successfully, but it hasn't. The damn input image has been locked by a COM surrogate and you have to go to your fooocus output folder and try and dig out the image that was supposed to have overwritten the original image.

A pain in the ass, because you have to check everytime you save the image now to see if it has successfully overwritten it or not.

It definitely never used to do this before.
I have w10 22h2 (totally uptodate).
I thought i'd mention it, even though Fooocus is practically Abandonware and this will never get fixed.

Steps to reproduce the problem

Inpaint, save the image over the file you are using as your source image. Sometimes works, sometimes does not.

What should have happened?

Save over the image, like it always used to

What browsers do you use to access Fooocus?

Mozilla Firefox

Where are you running Fooocus?

Locally

What operating system are you using?

No response

Console logs

I have no idea what this means

Additional information

No response