search

Avnsx / fansly-downloader

Easy to use fansly.com content downloading tool. Written in python, but ships as a standalone Executable App for Windows too. Enjoy your Fansly content offline anytime, anywhere in the highest possible content resolution! Fully customizable to download in bulk or single: photos, videos & audio from timeline, messages, collection & specific posts 👍
https://fansly.com/
GNU General Public License v3.0
1.28k stars 63 forks source link

line 1006, in hash_img PermissionError: [WinError 32] The process cannot access the file because it is being used by another process #106

Closed ForcedToRock closed 1 year ago

ForcedToRock commented 1 year ago

I just updated to version 0.4 and got that message when running the downloader. I was trying to update a previously scraped model profile.

Avnsx commented 1 year ago

Reboot pc, whitelist Fansly Downloader with your anti virus program and try again

ForcedToRock commented 1 year ago

Still have the issue.

Avnsx commented 1 year ago

Something is using the images it's trying to hash already. Are you trying to maybe run multiple versions of fansly downloader at once or something? Or maybe you're viewing some images, with another program while you're trying to run the downloader?

Or maybe the folder you set it to save the images to, fansly downloader is missing read and write permissions?

Maybe try starting fansly downloader as admin and see if that helps

ForcedToRock commented 1 year ago

The issue persisted, I couldn't remove the read-only option. I'd keep trying but it would revert to read-only. Weirdly, after starting again, it still showed that error message 3 times for GIF files located in the Messages>Videos directory, then the program ran just fine. Downloading stuff and whatnot.

Avnsx commented 1 year ago

I think I know why this happend, in line: https://github.com/Avnsx/fansly-downloader/blob/115d549204268db8a5bf6d7bd5b425c8add1d71c/fansly_downloader.py#L1003 I open the image with the python PIL module, but I forgot to close it. So the resource is not instantly released again, which might've caused this error.