ironfish icon indicating copy to clipboard operation
ironfish copied to clipboard

Out of memory error

Open omiDBaghi opened this issue 2 years ago • 1 comments

What happened?

The node exits due to out of memory error.

Version

0.1.44

Debug output

Iron Fish version               0.1.44 @ src
Iron Fish library               0.0.21 @ src
Operating system                Linux x64
CPU model(s)                    AMD EPYC Processor
CPU threads                     3
RAM total                       7.74 GiB
Heap total                      1.88 GiB
Node version                    v16.17.0
ironfish in PATH                true
Garbage Collector Exposed       true
Telemetry enabled               true
Node name                       omiD
Block graffiti                  omiD

Relevant log output

<--- Last few GCs --->

[6443:0x4ffc6e0] 757412071 ms: Mark-sweep 2020.4 (2083.9) -> 2019.2 (2083.9) MB, 1626.1 / 0.7 ms  (average mu = 0.112, current mu = 0.004) allocation failure scavenge might not succeed
[6443:0x4ffc6e0] 757413672 ms: Mark-sweep 2021.1 (2084.8) -> 2019.6 (2084.3) MB, 1596.1 / 0.8 ms  (average mu = 0.061, current mu = 0.003) allocation failure scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb09c10 node::Abort() [node]
 2: 0xa1c193 node::FatalError(char const*, char const*) [node]
 3: 0xcf8dbe v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xcf9137 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xeb09d5  [node]
 6: 0xeb14b6  [node]
 7: 0xebf9de  [node]
 8: 0xec0420 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xec339e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
10: 0xe848da v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
11: 0x11fd626 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x15f2099  [node]

Graffiti

omiD

omiDBaghi avatar Sep 18 '22 12:09 omiDBaghi

@omiDBaghi you are running an outdated version of Iron Fish. The latest release is v0.1.47. The last two releases have both included changes that aimed to address memory issues like the one you encountered here.

hughy avatar Sep 19 '22 21:09 hughy

@omiDBaghi you are running an outdated version of Iron Fish. The latest release is v0.1.47. The last two releases have both included changes that aimed to address memory issues like the one you encountered here.

Got the same problem on 0.1.49 today:

<--- Last few GCs --->

[6645:0x6327180] 81372513 ms: Mark-sweep 1995.1 (2081.0) -> 1979.3 (2081.3) MB, 5275.0 / 2.9 ms  (average mu = 0.194, current mu = 0.196) allocation failure scavenge might not succeed
[6645:0x6327180] 81379676 ms: Mark-sweep 1995.3 (2081.3) -> 1979.2 (2081.3) MB, 6250.9 / 5.1 ms  (average mu = 0.160, current mu = 0.127) allocation failure scavenge might not succeed


<--- JS stacktrace --->

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

wk27 avatar Oct 26 '22 13:10 wk27

Closing due to staleness. If the issue persists - please file a new issue

holahula avatar Apr 20 '23 22:04 holahula