[PR #10868] [MERGED] Jotty: increase RAM; cap heap size at 3GB during build #9062

Closed
opened 2026-02-26 16:35:01 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/10868
Author: @vhsdream
Created: 1/16/2026
Status: Merged
Merged: 1/16/2026
Merged by: @MickLesk

Base: mainHead: jotty


📝 Commits (1)

  • 393f31e Jotty: increase RAM; cap heap size at 3GB during build

📊 Changes

3 files changed (+8 additions, -4 deletions)

View changed files

📝 ct/jotty.sh (+4 -2)
📝 frontend/public/json/jotty.json (+1 -1)
📝 install/jotty-install.sh (+3 -1)

📄 Description

✍️ Description

  • Jotty was crashing when trying to update/install the latest few versions. RAM usage is pretty damn high, the only thing that works is increasing RAM to 4GB in conjunction with capping the max heap size (export NODE_OPTIONS="--max-old-space-size=3072"). I tried capping the heap size at 2GB and leaving RAM at 3GB but it still crashes.
  • Tested this on my install, and a fresh install from scratch.
  • Small formatting fix when removing files/dirs.

Fixes #

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/10868 **Author:** [@vhsdream](https://github.com/vhsdream) **Created:** 1/16/2026 **Status:** ✅ Merged **Merged:** 1/16/2026 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `jotty` --- ### 📝 Commits (1) - [`393f31e`](https://github.com/community-scripts/ProxmoxVE/commit/393f31e7979bc4e8a434b8a7e76035d35faff591) Jotty: increase RAM; cap heap size at 3GB during build ### 📊 Changes **3 files changed** (+8 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `ct/jotty.sh` (+4 -2) 📝 `frontend/public/json/jotty.json` (+1 -1) 📝 `install/jotty-install.sh` (+3 -1) </details> ### 📄 Description <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ Description - Jotty was crashing when trying to update/install the latest few versions. RAM usage is pretty damn high, the only thing that works is increasing RAM to 4GB in conjunction with capping the max heap size (`export NODE_OPTIONS="--max-old-space-size=3072"`). I tried capping the heap size at 2GB and leaving RAM at 3GB but it still crashes. - Tested this on my install, and a fresh install from scratch. - Small formatting fix when removing files/dirs. ## 🔗 Related Issue Fixes # ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [x] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [ ] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 16:35:01 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#9062
No description provided.