nextcloud / nextcloud/fulltextsearch
high CPU usage
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hi
I upgraded NC to 20.0.4 and now tesseract uses a Thread @100% since 2 weeks. Even after a restart. What can I do?
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 by checking the reported behavior after upgrading Nextcloud to 20.0.4 and identify which Tesseract thread remains at 100% CPU after a restart. The issue does not name a file, test, or entry point; done would require a confirmed cause and a reproducible fix or clear resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100