BUG: Updating Mail App exceeds Workers + CPU and terminates Nextcloud Service
Open
Nobody has claimed this yet.
0. to triage
bug
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- Wait for an update of this junk App
- Update Mail in bulk with other Apps
- Just wait a few seconds and prepare to restart the container
Bulk update without Mail-App install unobtrusive and succesfull.
Expected behavior
It should be possible to update the mailapp without shutting down the whole service
Actual behavior
Worker get exceeded CPU get exceeded
Mail app version
5.12.0
Nextcloud version
34.0.2
Mailserver or service
No response
Operating system
alpine
PHP engine version
PHP 8.3
Nextcloud memory caching
No response
Web server
None
Database
PostgreSQL
Additional info
I know as a user it is easy to criticise but this unreliability is beyond.
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
No files, tests, or entry points are identified in the report. Reproduce the bulk update with Mail 5.12.0 on Nextcloud 34.0.2 and PHP 8.3, then verify that updating Mail completes without exhausting workers or CPU or terminating the service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, postgresql
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100