Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Profiler enabled while application profiler is not

Open
#333 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
docker, php
Domain
tooling

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.

Description

https://github.com/juliushaertl/nextcloud-docker-dev/blob/dca6126821ffdc674333b87901236440669fe2e5/docker/configs/default.config.php#L12

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 ?

Dominant language
PHP
Stars
190
Forks
103
Avg merge
4h 36m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/nextcloud-docker-dev

All issues in nextcloud/nextcloud-docker-dev

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.