-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a timeout to preview generator. #489
Comments
I found out the issue i had. There was simply no File to generate, thats why i didn't seen anything in LSOF. files:scan --all and files:scan-app-data wasnt able to fix the issue, only user:delete was. There was no userfolder either, so previegenerate tryed to generate a preview for a non existing file. Cheers |
I had an issue where a corrupt video file somehow made it to one of the folders.
I had to delete the file manually, because the preview generation job would never complete. |
Yeah i have exactly the same fears, no matter what problem could happen, corrupted file or non existing one or whatever else can happen. A default timeout is a must! I don't really understand why there isn't such an basic option. Cheers |
It looks like i have a file, or other users (it's a txt file), where preview generator hangs forever.
Is it possible to add a simple timeout, so that previewgenerator doesn't hang forever to wait for the file?
Im using Previewgenerator in the Combination with Imaginary, but it seems that previewgenerator hangs itself, not imaginary.
generate-all hangs forever after this line:
Generating previews for /joerg.mustermann/files/test/audi Q3 code.txt
I would assume that particular file is fine, since that would still send it to imaginary, but according to "LSOF" the file it hangs on uses ImageMagick locally to generate an preview image. I just cant tell which file is the problematic one, since lsof doesnt show a particular file.
So in short, a simple Configurable timeout, like 10 Seconds, should solve the issue with broken files where preview-generator hangs on.
Cheers
The text was updated successfully, but these errors were encountered: