Closed gddrx closed 2 years ago
Some lines from my recent crashes:
SEND WebRtc DTFiU+k: NewTransaction (8) (repeated 2 times)
SEND WebSocket C2APnTc: NewTransaction (8) (repeated 2 times)
RECV WebRtc Hbp0tUr: NewTransaction (8) (repeated 70 times)
RECV WebRtc nfB76qB: NewTransaction (8) (repeated 55 times)
RECV WebRtc y0tWbtM: NewTransaction (8) (repeated 49 times)
RECV WebRtc OoVkhc9: NewTransaction (8) (repeated 46 times)
RECV WebRtc 8Rcs+tJ: NewTransaction (8) (repeated 70 times)
RECV WebRtc qk+TVjA: NewTransaction (8) (repeated 29 times)
RECV WebRtc Z8DxyOi: NewTransaction (8) (repeated 24 times)
RECV WebRtc xIPucuC: NewTransaction (8) (repeated 45 times)
<--- Last few GCs --->
[1643332:0x56e46c0] 62093929 ms: Mark-sweep 4017.2 (4134.2) -> 4002.1 (4134.5) MB, 2342.0 / 0.1 ms (average mu = 0.301, current mu = 0.255) allocation failure scavenge might not succeed
[1643332:0x56e46c0] 62097129 ms: Mark-sweep 4018.1 (4134.5) -> 4002.6 (4135.0) MB, 2083.6 / 0.2 ms (average mu = 0.325, current mu = 0.349) 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]
NPM installation method, Node.js v16.15.0, Ubuntu server 20.04.4 LTS, AMD Ryzen Threadripper PRO 3955WX 16-Cores, 512GB RAM, 931.5G swap partition. :-|
v0.1.39, nothing has changed, still the same error.
What is the behavior before you see the error? Does it run at all? Or does it take many hours/days before you see the error?
The node just works. But it is almost guaranteed to crash with such an error if you give it a day or two to work. Usually I constantly monitor it's status with ironfish status -f
command.
OK - we are currently working on memory management for long running cases like this. Should see some updates soon!
Please note that I have extended memory limit with export NODE_OPTIONS=--max_old_space_size=32768
and I'm still getting this error.
Duplicate of https://github.com/iron-fish/ironfish/issues/1925
v 0.1.15 This miner connected to my first server with node. Nothing do for repeat, but srv have 64Gb RAM+ 128Gb SWAP