nextcloud / nextcloud/fulltextsearch
Allowed memory size of 134217728 bytes exhausted
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
I got
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 1052672 bytes) in /var/www/nextcloud/apps/files_fulltextsearch/lib/Service/FilesService.php on line 319
I have 8GB memory - virtual server
after running awhile
real 11m15,892s
user 6m32,832s
sys 0m37,570s
Indexing ────
│ Action: generateIndexFiles
│ Provider: Files Account: christoph
│ Document: 5274
│ Info: /user/files/Shared/company/samba/talents/Talents Club/schicken
│ Title:
│ Content size:
│ Chunk: 1251/1540
│ Progress: 0/35005
I am surprised to see "generateIndexFiles" - its on the NC server - not the elastic server - which is healthy
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 with apps/files_fulltextsearch/lib/Service/FilesService.php around line 319 and follow the generateIndexFiles path during indexing. Reproduce the failure with the reported document and chunk progress, then determine where memory grows on the Nextcloud server rather than Elasticsearch. Done means the indexing run no longer ends with the PHP memory exhaustion error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100