starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Element Synapse install script fails due lack of memory #1359

New Issue
Closed
opened 2026-02-05 00:27:50 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 00:27:50 +03:00
Owner
Copy Link

Originally created by @tjcomserv on GitHub (Jul 28, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Element Synapse

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/elementsynapse.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Line 59 ("$STD yarn build") of elementsynapse-install.sh fails with the following:

... allocation failure; GC in old space requested
... JavaScript heap out of memory
... FatalProcessOutOfMemory

Changing the CT RAM to 2048MB the script runs fine. And then changing back to 1024MB seems to be ok.

I did not do a PR as I was unsure if there is a way to temporarily set the allocated RAM for the CT just for installation/build.

🔄 Steps to reproduce the issue.

Running the following fails:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/elementsynapse.sh)"

❌ Paste the full error output (if available).

[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1

[ERROR] in line 1305: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"var_install".sh)" ?

yarn run v1.22.22
$ vite build
vite v7.0.4 building for production...
transforming (12659) node_modules/lodash/_stackDelete.js
<--- Last few GCs --->

[364:0x187b1000] 22619 ms: Mark-Compact 504.4 (523.1) -> 500.7 (523.3) MB, pooled: 0 MB, 529.27 / 0.01 ms (average mu = 0.268, current mu = 0.141) allocation failure; scavenge might not succeed
[364:0x187b1000] 23328 ms: Mark-Compact 504.8 (523.6) -> 501.4 (524.3) MB, pooled: 0 MB, 628.97 / 0.02 ms (average mu = 0.189, current mu = 0.113) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0xe16044 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0x11e0dd0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0x11e10a7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x140e985 [/usr/bin/node]
5: 0x1428219 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
6: 0x13fc8c8 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]
7: 0x13fd7f5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]
8: 0x13d64ce v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/bin/node]
9: 0x1837aec v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]
10: 0x1d95476 [/usr/bin/node]
Aborted
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

🖼️ Additional context (optional).

No response

Originally created by @tjcomserv on GitHub (Jul 28, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Element Synapse ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/elementsynapse.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Line 59 ("$STD yarn build") of elementsynapse-install.sh fails with the following: ... allocation failure; GC in old space requested ... JavaScript heap out of memory ... FatalProcessOutOfMemory Changing the CT RAM to 2048MB the script runs fine. And then changing back to 1024MB seems to be ok. I did not do a PR as I was unsure if there is a way to temporarily set the allocated RAM for the CT just for installation/build. ### 🔄 Steps to reproduce the issue. Running the following fails: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/elementsynapse.sh)" ### ❌ Paste the full error output (if available). [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1 [ERROR] in line 1305: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"$var_install".sh)" $? ------ yarn run v1.22.22 $ vite build vite v7.0.4 building for production... transforming (12659) node_modules/lodash/_stackDelete.js <--- Last few GCs ---> [364:0x187b1000] 22619 ms: Mark-Compact 504.4 (523.1) -> 500.7 (523.3) MB, pooled: 0 MB, 529.27 / 0.01 ms (average mu = 0.268, current mu = 0.141) allocation failure; scavenge might not succeed [364:0x187b1000] 23328 ms: Mark-Compact 504.8 (523.6) -> 501.4 (524.3) MB, pooled: 0 MB, 628.97 / 0.02 ms (average mu = 0.189, current mu = 0.113) allocation failure; scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory ----- Native stack trace ----- 1: 0xe16044 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node] 2: 0x11e0dd0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node] 3: 0x11e10a7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node] 4: 0x140e985 [/usr/bin/node] 5: 0x1428219 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node] 6: 0x13fc8c8 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node] 7: 0x13fd7f5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node] 8: 0x13d64ce v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/bin/node] 9: 0x1837aec v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node] 10: 0x1d95476 [/usr/bin/node] Aborted error Command failed with exit code 134. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the buginvestigation labels 2026-02-05 00:27:50 +03:00
OVERLORD commented 2026-02-05 00:27:59 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 28, 2025):

Temporary not possible, Just do an PR and increase the RAM sources (in CT.sh and json)

@MickLesk commented on GitHub (Jul 28, 2025): Temporary not possible, Just do an PR and increase the RAM sources (in CT.sh and json)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug investigation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1359
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?