Skip to content
Snippets Groups Projects

Memory leaks with WS2P

    • Closed Issue created by Cédric Moreau @c-geek

    I've observed a significant memory usage increase on personal 24/24 7/7 UP nodes using 1.6 version of Duniter.

    Let's make some dumps with sudo kill -USR2 <pid>. Then compare the files with Chrom DevTools.

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Éloïs
      Éloïs @librelois ·
      Owner

      Indeed, one of my 1.6.8 nodes even spit out after a few days of execution :

      2017-10-06T01:59:06+02:00 - info: Node CGnyAA (185.167.16.19:10901) is UP!
2017-10-06T01:59:06+02:00 - info: Node 7G2mS5 (www.jouin.xyz:10901) is UP!
2017-10-06T01:59:16+02:00 - trace: Peer Com8rJukCozHZyFao6AheSsfDQdPApxQRnz7QYFf64mm is DOWN (ETIMEDOUT)
2017-10-06T01:59:16+02:00 - trace: Peer TENGx7WtzFsTXwnbrPEvb6odX2WnqYcnnrjiiLvp1mS is DOWN (ETIMEDOUT)
2017-10-06T01:59:18+02:00 - debug: Will check that node Com8rJ (g1.duniter.tednet.fr:8999) is UP in 1 min...
2017-10-06T01:59:18+02:00 - debug: Will check that node TENGx7 (remuniter.cgeek.fr:16120) is UP in 1 min...
2017-10-06T01:59:18+02:00 - trace: Checking if node GEWmVz is UP... (duniter.qbuissondebon.info:8999)
2017-10-06T01:59:18+02:00 - trace: Checking if node DJQjWd is UP... (88.162.208.159:34479)
2017-10-06T01:59:18+02:00 - trace: Checking if node 5dzkze is UP... (g1.duniter.vincentux.fr:8999)
2017-10-06T01:59:18+02:00 - trace: Checking if node 4Uz7X2 is UP... (77.157.127.54:59229)

<--- Last few GCs --->

373208841 ms: Scavenge 71.9 (86.1) -> 71.0 (93.1) MB, 3.5 / 0.0 ms [allocation failure].
373210747 ms: Scavenge 75.9 (94.1) -> 72.8 (95.1) MB, 2.2 / 0.0 ms [allocation failure].
373210923 ms: Scavenge 76.8 (95.1) -> 74.3 (96.1) MB, 11.1 / 0.0 ms [allocation failure].
373214000 ms: Scavenge 77.6 (96.1) -> 75.0 (96.1) MB, 3.3 / 0.0 ms [allocation failure].
373238328 ms: Scavenge 78.5 (97.1) -> 75.8 (91.1) MB, 6.4 / 0.0 ms (+ 61.4 ms in 28 steps since last GC) [allocation failure].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x67389c3fa99 <JS Object>
    2: PromiseEnqueue(aka PromiseEnqueue) [native promise.js:~98] [pc=0x3b19b2f69252] (this=0x67389c04241 <undefined>,y=0x67389c04241 <undefined>,C=0x2fd9715fff91 <JS Array[2]>,x=1)
    3: then [native promise.js:~215] [pc=0x3b19b11fd214] (this=0x2fd9715e5411 <a Promise with map 0x12c9fc9c3c1>,z=0x2fd9715ffcf1 <JS Function CreateResolveElementFunction (SharedFunctionInfo 0x2c3745cad171)>,A=0x2fd...

FATAL ERROR: Committing semi space failed. Allocation failed - process out of memory
 1: node::Abort() [/opt/duniter//node/bin/node]
 2: 0x109cafc [/opt/duniter//node/bin/node]
 3: v8::Utils::ReportApiFailure(char const*, char const*) [/opt/duniter//node/bin/node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/opt/duniter//node/bin/node]
 5: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/opt/duniter//node/bin/node]
 6: v8::internal::Heap::CollectGarbage(v8::internal::GarbageCollector, char const*, char const*, v8::GCCallbackFlags) [/opt/duniter//node/bin/node]
 7: v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/opt/duniter//node/bin/node]
 8: v8::internal::Runtime_AllocateInTargetSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/opt/duniter//node/bin/node]
 9: 0x3b19b11062bf
/usr/bin/duniter: line 15:  5793 Aborted                 $NODE "$DUNITER_DIR/bin/duniter" "$@"
    • Cédric Moreau mentioned in commit 8d51bc3c

      mentioned in commit 8d51bc3c

    • Cédric Moreau mentioned in commit df535606

      mentioned in commit df535606

    Please register or sign in to reply