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 11 Packages Projects Releases 10 Wiki Activity

Memos script isn´t working #622

New Issue
Closed
opened 2026-02-04 20:24:29 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 20:24:29 +03:00
Owner
Copy Link

Originally created by @steuerlexi on GitHub (Mar 13, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Memos

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/memos.sh)"

📝 Provide a clear and concise description of the issue.

The script gives an error at the end of its runtime

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

🔄 Steps to reproduce the issue.

after starting the script at the end i get this error

❌ Paste the full error output (if available).

memos@ postinstall /opt/memos/web
cd ../proto && buf generate

⠇
Done in 7.2s using pnpm v10.6.2
⠋

memos@ build /opt/memos/web
vite build

⠼vite v6.2.1 building for production...
✓ 5332 modules transformed.
⠏
<--- Last few GCs --->

[5758:0x24677000] 15270 ms: Scavenge 1008.8 (1039.0) -> 1006.6 (1039.0) MB, pooled: 1 MB, 2.81 / 0.00 ms (average mu = 0.193, current mu = 0.079) allocation failure;
[5758:0x24677000] 15296 ms: Scavenge 1009.4 (1039.5) -> 1007.6 (1048.7) MB, pooled: 0 MB, 4.72 / 0.00 ms (average mu = 0.193, current mu = 0.079) allocation failure;

<--- JS stacktrace --->

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

1: 0xe36196 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
2: 0x123f4a0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
3: 0x123f777 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
4: 0x146d1a5 [node]
5: 0x1486a19 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
6: 0x145b0e8 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
7: 0x145c015 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
8: 0x1434cee v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
9: 0x18962ec v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
10: 0x1df2476 [node]
⠋Aborted
 ELIFECYCLE  Command failed with exit code 134.
⠙
[ERROR] in line 58: exit code 0: while executing command $STD pnpm build

🖼️ Additional context (optional).

No response

Originally created by @steuerlexi on GitHub (Mar 13, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Memos ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/memos.sh)" ### 📝 Provide a clear and concise description of the issue. The script gives an error at the end of its runtime ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 🔄 Steps to reproduce the issue. after starting the script at the end i get this error ### ❌ Paste the full error output (if available). > memos@ postinstall /opt/memos/web > cd ../proto && buf generate ⠇ Done in 7.2s using pnpm v10.6.2 ⠋ > memos@ build /opt/memos/web > vite build ⠼vite v6.2.1 building for production... ✓ 5332 modules transformed. ⠏ <--- Last few GCs ---> [5758:0x24677000] 15270 ms: Scavenge 1008.8 (1039.0) -> 1006.6 (1039.0) MB, pooled: 1 MB, 2.81 / 0.00 ms (average mu = 0.193, current mu = 0.079) allocation failure; [5758:0x24677000] 15296 ms: Scavenge 1009.4 (1039.5) -> 1007.6 (1048.7) MB, pooled: 0 MB, 4.72 / 0.00 ms (average mu = 0.193, current mu = 0.079) allocation failure; <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory ----- Native stack trace ----- 1: 0xe36196 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node] 2: 0x123f4a0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node] 3: 0x123f777 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node] 4: 0x146d1a5 [node] 5: 0x1486a19 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node] 6: 0x145b0e8 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node] 7: 0x145c015 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node] 8: 0x1434cee v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node] 9: 0x18962ec v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node] 10: 0x1df2476 [node] ⠋Aborted  ELIFECYCLE  Command failed with exit code 134. ⠙ [ERROR] in line 58: exit code 0: while executing command $STD pnpm build ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:24:29 +03:00
OVERLORD commented 2026-02-04 20:24:45 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 13, 2025):

Heap Limit. Can you try an Install with more RAM?

@MickLesk commented on GitHub (Mar 13, 2025): Heap Limit. Can you try an Install with more RAM?
OVERLORD commented 2026-02-04 20:24:49 +03:00
Author
Owner
Copy Link

@steuerlexi commented on GitHub (Mar 13, 2025):

I ramped it up to 4GB Ram and that worked. Thank you!

@steuerlexi commented on GitHub (Mar 13, 2025): I ramped it up to 4GB Ram and that worked. Thank you!
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
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#622
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?