git ssb

Memory Leak Trace

Listening on http://localhost:7718/

<--- Last few GCs --->

[7925:0xb4ce2a0]   176810 ms: Scavenge 2037.9 (2052.5) -> 2032.7 (2052.7) MB, 4.6 / 0.0 ms  (average mu = 0.162, current mu = 0.110) allocation failure 
[7925:0xb4ce2a0]   176826 ms: Scavenge 2038.3 (2052.7) -> 2033.6 (2066.5) MB, 4.4 / 0.0 ms  (average mu = 0.162, current mu = 0.110) allocation failure 


<--- JS stacktrace --->

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

    0: ExitFrame [pc: 0x135bf99]
Security context: 0x25f3cd9408d1 <JSObject>
    1: /* anonymous */(aka /* anonymous */) [0x7cde23cce91] [/home/fabian/.local/node/lib/node_modules/git-ssb/node_modules/pull-goodbye/node_modules/pull-stream/throughs/filter.js:~14] [pc=0x2e33b64f6c1c](this=0x128377a404b1 <undefined>,0x128377a401b9 <null>,0x07cde23cd001 <Object map = 0x2e61674e5a09>)
    2: cb [0x7cde23cd049] [/home/fabian/.local/node/lib/nod...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x982a88 node::Abort() [node]
 2: 0x8ba39d  [node]
 3: 0xb1a832 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xb1aaee v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xcbf815  [node]
 6: 0xcd29ec v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
 7: 0xcd36eb v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 8: 0xcd3afc v8::internal::Heap::CollectAllGarbage(int, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xc82f8d v8::internal::StackGuard::HandleInterrupts() [node]
10: 0xfdedef v8::internal::Runtime_StackGuard(int, unsigned long*, v8::internal::Isolate*) [node]
11: 0x135bf99  [node]
error: git-ssb died of signal 6

@Fabián Heredia Montiel does it happen when viewing any specific repo(s) or files?

@cel, I had just launched git ssb web and attempted to load two of the first repos that showed up. However I haven't been able to replicate the issue.

Apparently only a one off issue.

@Fabián Heredia Montiel Ok. Thanks for reporting it anyway.