Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Severe browser freeze (3GB+ RAM spike) when closing Viewer in Deck boards with high attachment counts

オープン
  • 何か問題がありますか？
#8,539 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
30/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript
領域
frontend, performance

調査の方向性

The report points at the Viewer overlay that opens from a Deck card attachment and at the list of attachments it builds for the board, including archived cards. Start by reproducing with a board that has many image attachments and watching memory in the browser profiler while closing the Viewer. Done means closing the Viewer no longer causes the memory spike, and the attachment list is limited to what the slideshow needs.

索引モデルが issue の本文から書いたものです。

説明

0. Needs triage bug
How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Describe the bug
When viewing an image attachment in a Deck board that contains a massive number of total attachments (accumulated over 2+ years), closing the Viewer app (clicking the "X") causes a severe Javascript memory leak. The browser tab's RAM usage violently spikes—sometimes upwards of 3GB—and completely locks up/freezes the tab
This appears to be a garbage collection/DOM teardown issue caused by the Viewer app loading a massive background array of every single attachment associated with the Board ID, including attachments on Archived cards.

To Reproduce
teps to reproduce the behavior:

1. Operate a Deck board with thousands of image attachments (JPG/PNG).

2. Archive the vast majority of the cards containing these attachments over time.

3. Left-click an image attachment on an active card to open the Nextcloud Viewer overlay.

4. Click the "X" in the top right to close the Viewer.

Observe the system task manager: The browser tab's RAM usage spikes to 3GB+ and the tab completely freezes for an extended period while the JS engine attempts garbage collection.

Expected behavior
The Viewer should close instantly with minimal memory overhead, regardless of how many attachments are on the board. Ideally, the Viewer should paginate the slideshow array or exclude attachments from Archived cards entirely to prevent the payload from growing infinitely and causing a 3GB memory spike over the lifespan of a board.

Screenshots
If applicable, add screenshots to help explain your problem.

Client details:

  • OS: Many diffrent OS's, Mac, Linux (ubuntu, solus, fedora) and Windows
  • Browser firefox, chrome
  • Version 34.0.4 SNAP
  • Device: desktop
Server details

Operating system:
Ubuntu 24.04.5 LTS x86_64

Nextcloud version: (see Nextcloud admin page)
34.0.4 (installed from snap)
Where did you install Nextcloud from:
snap store

Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.

No Errors Found.

List of activated apps:
Enabled:

  • activity: 7.0.0
  • admin_audit: 1.24.0
  • announcementcenter: 7.5.1
  • appstore: 1.0.0
  • bookmarks: 16.2.7
  • bruteforcesettings: 7.0.0
  • calendar: 6.6.2
  • cloud_federation_api: 1.18.0
  • comments: 1.24.0
  • contacts: 8.9.1
  • contactsinteraction: 1.15.0
  • dashboard: 7.14.0
  • dav: 1.40.0
  • deck: 1.18.5
  • external: 9.0.1
  • federatedfilesharing: 1.24.0
  • files: 2.6.0
  • files_downloadlimit: 5.2.0
  • files_external: 1.26.0
  • files_lock: 34.0.1
  • files_pdfviewer: 7.0.0
  • files_reminders: 1.7.0
  • files_sharing: 1.26.0
  • files_trashbin: 1.24.0
  • files_versions: 1.27.0
  • firstrunwizard: 7.0.0-dev.0
  • forms: 5.4.0
  • groupfolders: 22.0.6
  • guests: 4.10.0
  • integration_giphy: 2.3.0
  • logreader: 7.0.0
  • lookup_server_connector: 1.22.0
  • nextcloud_announcements: 6.0.0
  • notes: 6.1.0
  • notifications: 7.0.0-dev.1
  • oauth2: 1.22.0
  • office: 1.0.0
  • password_policy: 6.0.0-dev.0
  • passwords: 2026.10.20
  • previewgenerator: 5.15.0
  • privacy: 6.0.0-dev.1
  • profile: 1.3.0
  • provisioning_api: 1.24.0
  • related_resources: 5.0.0-dev.0
  • richdocuments: 11.1.2
  • richdocumentscode: 26.4.402
  • serverinfo: 6.0.0
  • settings: 1.17.0
  • sharebymail: 1.24.0
  • spreed: 24.0.5
  • support: 6.0.0
  • survey_client: 6.0.0-dev.0
  • systemtags: 1.24.0
  • tasks: 0.18.1
  • text: 8.0.0
  • theming: 2.9.0
  • theming_customcss: 1.22.0
  • twofactor_backupcodes: 1.23.0
  • twofactor_totp: 16.0.0
  • user_status: 1.14.0
  • viewer: 7.0.0-dev.0
  • weather_status: 1.14.0
  • webhook_listeners: 1.6.0
  • workflowengine: 2.16.0
    Disabled:
  • app_api: 34.0.0 (installed 32.0.0)
  • circles: 34.0.0 (installed 29.0.0-dev)
  • encryption: 2.22.0 (installed 2.22.0)
  • federation: 1.24.0 (installed 1.24.0)
  • mail: 5.12.4 (installed 5.12.4)
  • metadata: 0.24.0 (installed 0.24.0)
  • photos: 7.0.0 (installed 5.0.0)
  • recommendations: 7.0.0 (installed 4.0.0)
  • suspicious_login: 12.0.0-dev.0 (installed 5.0.0)
  • twofactor_nextcloud_notification: 8.0.0
  • user_ldap: 1.25.0
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

Nextcloud configuration:

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or

Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...

Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...
主要言語
JavaScript
スター
1.4k
フォーク
358
平均マージ
2日 18時間
マージ済み PR（30日）
83

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nextcloud/deck のほかの issue

nextcloud/deck の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。