Fatal error: ineffective mark-compacts near heap limit allocation failed - Javascript heap out of memory

I am trying to convert a rather long (~80 s) cast to svg, but I am hitting a memory issue:

mathieu@xiaomimi-solus ~ $ npx svg-term-cli --cast=336443 --out asciicast-nnn.svg --window
npx: installed 201 in 9.255s

<--- Last few GCs --->

[548208:0x396a570]    92078 ms: Scavenge 1786.8 (2059.9) -> 1775.1 (2062.1) MB, 16.7 / 0.0 ms  (average mu = 0.268, current mu = 0.222) allocation failure 
[548208:0x396a570]    92191 ms: Scavenge 1792.9 (2062.1) -> 1781.2 (2064.4) MB, 18.1 / 0.0 ms  (average mu = 0.268, current mu = 0.222) allocation failure 
[548208:0x396a570]    92296 ms: Scavenge 1799.4 (2064.4) -> 1787.5 (2066.6) MB, 18.4 / 0.0 ms  (average mu = 0.268, current mu = 0.222) allocation failure 


<--- JS stacktrace --->

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

   0: ExitFrame [pc: 0x1296b99]
Security context: 0x25bdbbac08a1 <JSObject>
   1: p [0x2485eba27579] [/home/mathieu/.npm/_npx/548208/lib/node_modules/svg-term-cli/node_modules/load-asciicast/index.js:~2044] [pc=0x23eff06629e](this=0x3d169de03061 <JSGlobal Object>,0x3f7693688399 <JSObject>)
   2: /* anonymous */ [0x1c49ead282d1] [/home/mathieu/.npm/_npx/548208/lib/node_modules/svg-term-cli/node_modules/load-asciicast/index.js:~1204] [pc...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Writing Node.js report to file: report.20200604.131906.548208.0.001.json
Node.js report completed
1: 0x91b658 node::Abort() [svg-term]
2: 0x91caa1 node::OnFatalError(char const*, char const*) [svg-term]
3: 0xa93a32 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [svg-term]
4: 0xa93cee v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [svg-term]
5: 0xc20e35  [svg-term]
6: 0xc33dac v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [svg-term]
7: 0xc34aab v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [svg-term]
8: 0xc36f3c v8::internal::Heap::AllocateRawWithLightRetry(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [svg-term]
9: 0xc37261 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [svg-term]
10: 0xbfc9e9 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType) [svg-term]
11: 0xf33f42 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [svg-term]
12: 0x1296b99  [svg-term]
Aborted

Is the conversion for that kind of long cast totally unrealistic? Would the end file be huge if there are not too many colours in the original cast? What I would like to do is embed the animation in a README page for demo, which is not doable with the base asciinema cast format.

[skyzyx]

export NODE_OPTIONS="--max-old-space-size={megabytes}"

[Kabouik]

Excellent, thanks. It took ages with my long cast but it worked without optimization, and the final .svg file is about 6.5 MB.