Sandbox is not deleted if an error occurs during a process

Created on 5 September 2025, about 22 hours ago

Problem/Motivation

In testing per 🐛 Composer errors using Project Browser on Hostarmada Active , after hitting this error, the sandbox was not removed. So file usage went from 48k (post-install) -> 96k, then if you try again you get another 48k files and quickly hit the limit of 250,000, at which point everything breaks.

Steps to reproduce

Not so easy I guess, but on shared hosting, try to run a package manager task, e.g. adding a module. If there is an error, check that the sandbox and files still exist in tmp and the number of files in your instance has doubled.

Proposed resolution

TBC

Remaining tasks

TBC

User interface changes

N/A

Introduced terminology

N/A

API changes

N/A

Data model changes

N/A

Release notes snippet

N/A

🐛 Bug report

Status

Active

Version

11.0 🔥

Component

package_manager.module

Created by

🇦🇺Australia pameeela

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @pameeela
Comment about 21 hours ago →
🇦🇺Australia pameeela
This is wrong! I just realised it only gets deleted on cron runs. So I think there is still a problem here as it can easily still fill up if you try PB a few times before cron is able to run, but will close this and open a fresh issue with more info on that.
Comment about 21 hours ago →
System Message
Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024