nextcloud / nextcloud/text

Long documents slow Chrome/Chromium to a halt

Open
#5,819 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug high performance 🚀
Dominant language
JavaScript
Stars
659
Forks
133
Avg merge
1d 20h
Merged PRs (30d)
110

Description

While longer markdown documents are not super fast in any browser, there seems to be an overlap of performance-eating bugs or circumstances when opening long (>1000 lines) markdown files.

To Reproduce
Steps to reproduce the behavior:

  1. Create a files with a variety of headlines, plain-text, and lists with sub-lists that is at least 10000 lines long. It doesn't have to be particular complicated, but long.
  2. Open it in Chromium.
  3. Wait a long time for it to render at all.
  4. Wait a few seconds every time you try to scroll or edit the document.

Expected behavior
A maybe slow, but not unusable document.

Server details:

  • Nextcloud version: 29.0.0.19 and 29.0.1 RC1
  • PHP Version: 8.2
  • Database: PostgreSQL 15.6
  • Text app version: 3.10.0

Client details:

  • OS: various Linuxes (Ubuntu, Arch, Debian)
  • Browser: Chromium
  • Browser version: 125, 126, and others
  • Device: various laptops
Logs
Nextcloud log (data/nextcloud.log)

No related server-side logs. This issue appears to be entirely client-side.

Browser log

Console and Network tab are pretty quiet, but the Performance tab shows a lot of activity. We can provide the corresponding json file if this issue can't be reproduced by anyone else.

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 with a 10,000-line Markdown document containing headings, text, and nested lists in Chromium, then inspect the browser Performance tab. The issue names no source file or test; done means the document opens, scrolls, and remains editable without becoming unusably slow.

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.