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

out of memory at 4Gb #1163

Closed
michielbdejong opened this issue Sep 10, 2024 · 2 comments
Closed

out of memory at 4Gb #1163

michielbdejong opened this issue Sep 10, 2024 · 2 comments

Comments

@michielbdejong
Copy link
Member

2024-09-10 11:02:55 info  Paprika — Terms of Service                                                  No changes after filtering, did not record version
2024-09-10 11:02:57 info  Parcel — Privacy Policy                                                     No changes after filtering, did not record version
2024-09-10 11:02:58 info  Parchment — Privacy Policy                                                  No changes after filtering, did not record version
2024-09-10 11:03:00 info  Parchment — Terms of Service                                                No changes after filtering, did not record version

<--- Last few GCs --->

[33319:0x659f4c0]  3826770 ms: Mark-Compact (reduce) 1965.2 (1997.9) -> 1964.3 (1996.2) MB, 134.04 / 0.01 ms  (+ 22.3 ms in 26 steps since start of marking, biggest step 20.5 ms, walltime since start of marking 187 ms) (average mu = 0.395, current mu = 0.[33319:0x659f4c0]  3826970 ms: Mark-Compact (reduce) 1965.4 (1996.2) -> 1964.5 (1996.7) MB, 81.25 / 0.01 ms  (+ 55.7 ms in 15 steps since start of marking, biggest step 28.8 ms, walltime since start of marking 177 ms) (average mu = 0.359, current mu = 0.3

<--- JS stacktrace --->

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

 1: 0xb86ecf node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
 2: 0xef74d0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
 3: 0xef77b7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
 4: 0x1109355  [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
 5: 0x11211d8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
 6: 0x10f72f1 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
 7: 0x10f8485 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
 8: 0x10d5ad6 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
 9: 0x1531906 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
10: 0x196aef6  [/home/crawler/.nvm/versions/node/v20.17.0/bin/node]
@michielbdejong
Copy link
Member Author

NODE_OPTIONS=--max_old_space_size=8000 npx ota track

@michielbdejong
Copy link
Member Author

We're now using a server with 8Gb memory anyway, but this NODE_UPTIONS would probably also make it possible to run in a 4Gb server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant