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.

JavaScript heap out of memory

See original GitHub issue

I have just installed enex-dump (ubuntu 18.04) and tried to convert an ENEX file containing a few hundred notes (~373 MB, since it has quite a few attachments). The following is the output:

mbentley@bpcl03:~/Desktop$ enex-dump --src notes.enex --dst notes

<--- Last few GCs --->

[17938:0x55d3d37c3220]     1977 ms: Mark-sweep 762.3 (800.8) -> 760.6 (800.8) MB, 9.5 / 0.0 ms  allocation failure GC in old space requested
[17938:0x55d3d37c3220]     1991 ms: Mark-sweep 760.6 (800.8) -> 760.5 (765.8) MB, 14.3 / 0.0 ms  last resort GC in old space requested
[17938:0x55d3d37c3220]     2007 ms: Mark-sweep 760.5 (765.8) -> 760.5 (765.8) MB, 15.3 / 0.0 ms  last resort GC in old space requested


<--- JS stacktrace --->

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

Security context: 0x22aaad598fe1 <JSObject>
    2: replace(this=0x79116f82201 <Very long string[390176708]>,0x1f5d1adc22d9 <JSRegExp <String[15]: <!--[\s\S]*?-->>>,0x22aaad582801 <String[0]: >)
    3: getTraversalObj [/usr/local/lib/node_modules/enex-dump/node_modules/fast-xml-parser/src/xmlstr2xmlnode.js:72] [bytecode=0x395c79c21b11 offset=45](this=0x3330a949851 <Object map = 0x32869ea758f9>,xmlData=0x79116f82201 <Very long string[390176...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0x55d3d16f8011 [node]
 3: v8::Utils::ReportOOMFailure(char const*, bool) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
 5: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [node]
 6: 0x55d3d15adb54 [node]
 7: v8::internal::Runtime_StringReplaceGlobalRegExpWithString(int, v8::internal::Object**, v8::internal::Isolate*) [node]
 8: 0x5bab79040bd

Aborted (core dumped)

Any clues? Thanks!!

Issue Analytics

State:
Created 4 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

fabiospampinatocommented, Jul 22, 2019

I think this issue got fixed for the most part in the rewrite.

0reactions

fabiospampinatocommented, Apr 29, 2019

I’m reopening as this should be fixed on the library-side, it should just work.

Top Results From Across the Web

How to Fix JavaScript Heap Out of Memory Error - MakeUseOf

A common problem while working on a JavaScript Node.js project is the “JavaScript heap out of memory” error. This error usually occurs when ......

Node.js heap out of memory - javascript - Stack Overflow

I have a 64-bit CPU and I've installed x86 node version, which caused the CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory ......

JavaScript heap out of memory - Snyk Support

This generally occurs on larger projects where the default amount of memory allocated by Node (1.5gb) is insufficient to complete the command successfully....

How to solve JavaScript heap out of memory error

To fix JavaScript heap out of memory error, you need to add the --max-old-space-size option when running your npm command. ... Alternatively, you ......

JavaScript Heap Out Of Memory Error - OpenReplay Blog

A quick solution that you can use to fix "Heap Out Of Memory Error" in JavaScript. We lay out the causes and how...