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.

Sign up for GitHub

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

Jump to bottom

OOM error indexing many blocks #44

Open
betaprior opened this issue May 18, 2020 · 0 comments
Open

OOM error indexing many blocks #44

betaprior opened this issue May 18, 2020 · 0 comments

Comments

@betaprior
Copy link

After turning on the logger on a Fabric system that's been up for a while I saw an OOM crash after ~5,000 blocks were indexed.

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

    0: ExitFrame [pc: 0x396f358078a1]
Security context: 0x3bbde5ef3841 <JSObject>
    1: byteLength [0x210470cf96c1] [buffer.js:~509] [pc=0x396f358eb407](this=0x210470cd31f1 <JSFunction Buffer (sfi = 0x7bfb415ff9)>,string=0x0e5d7c0523e1 <Very long string[41627931]>,encoding=0x14d0afc4d971 <String[4]: utf8>)
    2: send [0x35254f3ea0a9] [/home/ubuntu/splunk-fabric-logger/fabric-logger/node_modules/splunk-logging/splunklogger.js:559] [bytec...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@betaprior