question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Heap out of memory when reading events from file (50,000 tests)

See original GitHub issue

Running a massive set of tests, I get this:

  51973 passing (5h)

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node_module_register
 2: v8::internal::FatalProcessOutOfMemory
 3: v8::internal::FatalProcessOutOfMemory
 4: v8::internal::Factory::NewUninitializedFixedArray
 5: v8::internal::WasmDebugInfo::SetupForTesting
 6: v8::internal::interpreter::BytecodeArrayRandomIterator::UpdateOffsetFromIndex
 7: 000001FEEE7043C1

The contents of file .solcover.js:

module.exports = {
    port:           8555,
    norpc:          true,
    testCommand:    "node --max-old-space-size=8192 ../../node_modules/truffle/build/cli.bundled.js test --network=coverage",
    compileCommand: "node --max-old-space-size=8192 ../../node_modules/truffle/build/cli.bundled.js compile --network=coverage",
};

Environment:

  • Windows 10
  • node 8.11.2
  • npm 6.1.0

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
cgeweckecommented, Jun 24, 2018

@barakman Modified your issue title to disambiguate your case from the one we already advise about in the FAQ.

I don’t know how to fix this. If anyone has any ideas, please weigh in.

0reactions
barakmancommented, Jan 1, 2020

@cgewecke: You’re welcome. This one in specific has been both exhilarating and excruciating to investigate and resolve (well, workaround)… As a matter of fact, in terms of difficulty, I believe that it was second to Truffle 4 issue 729 only. Thank you for providing this outstanding tool, which IMO is a must in every Ethereum project. Happy New Year 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

JavaScript Heap Out Of Memory Error | Felix Gerschau
This error indicates high memory usage or a memory leak in your application. In this article, I cover different solutions to this problem....
Read more >
7 Problems to Look out for When Analyzing Garbage ...
7 Problems to Look out for When Analyzing Garbage Collection Logs · 1. GC pauses cause apps to stall · 2. Memory leaks...
Read more >
why does attempting to write a large file cause js heap to run ...
The out of memory error happens because you're not waiting for the drain event to be emitted, without waiting Node.js will buffer all ......
Read more >
Off-Heap memory reconnaissance - Brice Dutheil
I faced a few incidents, where the JVM settings and the Kubernetes memory limit were seemingly appropriate, yet the apps were constantly OOM ......
Read more >
limits.conf - Splunk Documentation
If the memory limit is exceeded, output is truncated, not spilled to disk. ... this limits the number of event entries read from...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found