nextcloud / nextcloud/recognize
Recognition Cannot Get Past Image
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 699
- Forks
- 68
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
Which version of recognize are you using?
10.0.6
Enabled Modes
Object recognition, Face recognition
TensorFlow mode
WASM mode
Downstream App
Photos App
Which Nextcloud version do you have installed?
32.0.1
Which Operating system do you have installed?
Ubuntu 24.04
Which database are you running Nextcloud on?
Postgres?
Which Docker container are you using to run Nextcloud? (if applicable)
AIO
How much RAM does your server have?
4 GB
What processor Architecture does your CPU have?
x86
Describe the Bug
Recognize errors on one particular image, and cannot move past it. Face and Object recognition halts.
From the Nextcloud Logs:
Allowed memory size of 536870912 bytes exhausted (tried to allocate 65536 bytes) at /var/www/html/custom_apps/recognize/lib/Classifiers/Classifier.php#389
Failed to generate preview of 18666 with dimension 1024 with nextcloud preview manager: No provider successfully handled the preview generation
The above just repeats every 6 hours. Same number 18666.
Expected Behavior
Fail x number of times, put it aside, and then move on.
To Reproduce
Not sure what to tell you. The image 18666 (if I'm identifying it correctly), is quite large: a 23 MB JPG. 15,600x15,600 pixels. It's not under "Photos", is a digital drawing, and doesn't have any faces or objects to recognize.
Debug log
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at lib/Classifiers/Classifier.php around line 389 and inspect the repeated preview-generation failure for image 18666. Reproduce with the reported 23 MB, 15,600×15,600 JPG in WASM mode, then verify that a failing image is skipped after bounded retries and recognition continues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php, tensorflow, wasm
- Domain
- backend, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100