Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Proxmox Update Script fails #81

Closed
splnut opened this issue Apr 3, 2024 · 2 comments
Closed

[BUG] Proxmox Update Script fails #81

splnut opened this issue Apr 3, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@splnut
Copy link

splnut commented Apr 3, 2024

Environment

Other (Specify below)

System

Proxmox 8.1.5

Version

11.0

Describe the problem

LXC was built using tteck's script and is running 11.0 just fine. When running the script inside the LXC console, I'm receiving the following error.

<--- Last few GCs --->

[465:0x57870f0] 84370 ms: Mark-Compact 492.4 (521.9) -> 487.9 (521.5) MB, 646.78 / 0.00 ms (average mu = 0.182, current mu = 0.136) allocation failure; scavenge might not succeed
[465:0x57870f0] 85004 ms: Mark-Compact 492.6 (522.3) -> 489.0 (522.6) MB, 607.69 / 0.00 ms (average mu = 0.118, current mu = 0.042) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0xb84bd6 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xefead0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xefedb7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x11107c5 [/usr/bin/node]
5: 0x1110d54 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x1127c44 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x112845c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10fe761 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]
9: 0x10ff8f5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]
10: 0x10dcf46 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/bin/node]
11: 0x1537cd6 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]
12: 0x1971ef6 [/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.

[ERROR] in line 68: exit code 0: while executing command yarn build

Additional info

No response

@splnut splnut added the bug Something isn't working label Apr 3, 2024
@hywax
Copy link
Owner

hywax commented Apr 11, 2024

Apparently you do not have enough memory to rebuild the project. Try to allocate 512-1024mb.

@splnut
Copy link
Author

splnut commented Apr 12, 2024

I doubled the default ram and all is good.

@splnut splnut closed this as completed Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants