nextcloud / nextcloud/mail

Memory leak in browser when opening a large mailbox that has not been opened before

Open
#6,718 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Steps to reproduce
  1. Go to mail
  2. Navigate to a mailbox (with more than 1.5k emails) that has not been opened at all or opened a long time ago
Expected behavior

Open the mailbox. Wait for the sync and show messages. Memory could go up but should be released after a while.

Actual behavior

the tab or chrome will eventually stop responding eating away at 2.5gb or ram

Mail app version

1.13.3

Mailserver or service

Dovecot

Operating system

Debian 11

PHP engine version

PHP 8.0

Web server

Nginx

Database

MariaDB

Additional info

Using google chrome Version 102.0.5005.61 (Official Build) (64-bit)

Screenshot from 2022-06-10 12-10-18
Screenshot from 2022-06-10 12-04-45
Screenshot from 2022-06-10 12-03-17
Screenshot from 2022-06-10 12-00-13

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 by reproducing the issue in Chrome using the listed steps with a mailbox containing more than 1.5k emails, then observe memory use during synchronization. Done means the mailbox opens and syncs while the tab remains responsive and memory is released after the operation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.