nextcloud / nextcloud/server

[Bug]: `occ files:sanitize-filenames --dry-run` out of memory fatal error

Open
#53,433 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 31-feedback bug feature: filesystem feature: occ hotspot: filename handling performance 🚀
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

When running occ files:sanitize-filenames --dry-run, after some time, the command crash with a fatal error.
see
PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in <path>/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php on line 131

Steps to reproduce
  1. cd
  2. sudo -u php ./occ files:sanitize-filenames --dry-run`
Expected behavior

the command completes the dry run

Nextcloud Server version

31

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

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.

Research direction

Start with the occ files:sanitize-filenames --dry-run entry point and reproduce the failure using the command and environment described. Inspect lib/private/AppFramework/Utility/SimpleContainer.php around line 131 to trace the memory growth; done means the dry run completes without the fatal out-of-memory error.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.