Skip to content
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

Face recognition stalled because of an 800MB .tif file #1227

Open
brupje opened this issue Dec 24, 2024 · 1 comment
Open

Face recognition stalled because of an 800MB .tif file #1227

brupje opened this issue Dec 24, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@brupje
Copy link

brupje commented Dec 24, 2024

Which version of recognize are you using?

8.2.0

Enabled Modes

Face recognition, Object recognition, Video recognition, Music recognition

TensorFlow mode

Normal mode

Downstream App

Memories App

Which Nextcloud version do you have installed?

30.0.4

Which Operating system do you have installed?

Ubuntu 24.04.1 LTS

Which database are you running Nextcloud on?

MySQL

Which Docker container are you using to run Nextcloud? (if applicable)

n/a

How much RAM does your server have?

32gb

What processor Architecture does your CPU have?

amd64

Describe the Bug

Noticed that the face recognition wasn't working. Investigated a bit and
sudo -u www-data php8.3 occ background-job:execute 107166 --force-execute
said:

Forcing execution of the job

free(): invalid next size (fast)
Aborted

Added some debug into ClassifyFacesJob.php to find out which file caused the problem and removing a 800MB .tif file allowed the process to continue. I don't mind it is failing to scan one file, but this shouldn't cause the background to stall and keep retrying the same file.

Expected Behavior

If a subprocess crashes, the offending file(s) should be logged and ignored.

To Reproduce

Upload a files that fails to load and crashes the subprocess. Facial detection will never complete now.

Debug log

No response

@brupje brupje added the bug Something isn't working label Dec 24, 2024
Copy link

Hello 👋

Thank you for taking the time to open this issue with recognize. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself. (Also see our Code of Conduct. Really.)

I look forward to working with you on this issue
Cheers 💙

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant