nextcloud / nextcloud/nextcloud-docker-dev
Profiler enabled while application profiler is not
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 190
- Forks
- 103
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 1
Description
The default configuration enables the profiler, even if the profiler application is not there.
Because of that, sync jobs for LDAP users are running out of memory, because the profile data fills it up. I chased a memory leak before finding out this was simply profiling data, as I was not aware the profiler was enabled.
WDYT @juliushaertl ?
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 docker/configs/default.config.php, especially line 12, and inspect how the default configuration enables the profiler. Confirm whether the profiler application is present in this development environment, then adjust the default setting so profiling is not enabled when it is unavailable. Done means LDAP sync jobs no longer accumulate profiler data under this configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100