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

terminated by signal SIGABRT #1225

Closed
abhishiv opened this issue Mar 8, 2020 · 2 comments
Closed

terminated by signal SIGABRT #1225

abhishiv opened this issue Mar 8, 2020 · 2 comments
Labels
bug Functionality does not match expectation

Comments

@abhishiv
Copy link

abhishiv commented Mar 8, 2020

Unfortunately can't make public the source repo. But here's the stacktrace.


<--- Last few GCs --->

[4286:0x105002600]   104823 ms: Mark-sweep 2058.2 (2064.7) -> 2058.1 (2064.7) MB, 1351.9 / 0.0 ms  (average mu = 0.063, current mu = 0.000) last resort GC in old space requested


<--- JS stacktrace --->

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

    0: ExitFrame [pc: 0x1006db52d]
Security context: 0x0ce93c000921 <JSObject>
    1: toString [0xce9f846ef09] [buffer.js:~756] [pc=0x195c047b9962](this=0x0ce95ead40e9 <Uint8Array map = 0xce94cea3ee1>,0x0ce9f8467cb9 <String[#4]: utf8>,0x0ce9d93004b9 <undefined>,0x0ce9d93004b9 <undefined>)
    2: arguments adaptor frame: 1->3
    3: readFileWorker(aka readFileWorker) [0xce9e294f259] [/Users/abhishiv/work/gratico/leela/node_modules/typedoc/...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x100b9f982 node::Abort() (.cold.1) [/usr/local/bin/node]
 2: 0x100084338 node::FatalError(char const*, char const*) [/usr/local/bin/node]
 3: 0x100084460 node::OnFatalError(char const*, char const*) [/usr/local/bin/node]
 4: 0x10017dfc1 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 5: 0x10017df6b v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 6: 0x100297f23 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
 7: 0x1002992a8 v8::internal::Heap::MarkCompactPrologue() [/usr/local/bin/node]
 8: 0x100296e76 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
 9: 0x100295955 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
10: 0x100295bd2 v8::internal::Heap::CollectAllAvailableGarbage(v8::internal::GarbageCollectionReason) [/usr/local/bin/node]
11: 0x10029d36d v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
12: 0x10027a4f5 v8::internal::Factory::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [/usr/local/bin/node]
13: 0x10027c8e8 v8::internal::Factory::NewRawOneByteString(int, v8::internal::AllocationType) [/usr/local/bin/node]
14: 0x10027c997 v8::internal::Factory::NewStringFromUtf8(v8::internal::Vector<char const> const&, v8::internal::AllocationType) [/usr/local/bin/node]
15: 0x100195e8b v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [/usr/local/bin/node]
16: 0x10010e6df node::StringBytes::Encode(v8::Isolate*, char const*, unsigned long, node::encoding, v8::Local<v8::Value>*) [/usr/local/bin/node]
17: 0x10006ba10 void node::Buffer::(anonymous namespace)::StringSlice<(node::encoding)1>(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
18: 0x1006db52d Builtins_CallApiCallback [/usr/local/bin/node]
fish: './node_modules/.bin/typedoc  --…' terminated by signal SIGABRT (Abort)

Environment

  • Typedoc version: 0.16.11
  • Typescript version: TypeScript 3.7.5
  • Node.js version: v13.5.0
  • OS: OSX
@abhishiv abhishiv added the bug Functionality does not match expectation label Mar 8, 2020
@Gerrit0
Copy link
Collaborator

Gerrit0 commented Mar 10, 2020

I'm afraid there isn't much I can do here without a reproduction... the stacktrace doesn't reveal much about the potential memory leak. The last bug that caused this was #1150, where a recursive type wasn't handled properly by TypeDoc. Are you using any recursive types by any chance?

@abhishiv
Copy link
Author

Hey @Gerrir0, ok I understand. Just FYI --excludeExternals fixed it for me, so maybe it was something in my node_modules causing this.

closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality does not match expectation
Projects
None yet
Development

No branches or pull requests

2 participants