Open nhha1602 opened 4 years ago
Hi @nhha1602 ,
Looks like JavaScript heap out of memory
error is probably because of a limit set by V8 engine. reference, let me know if you can overcome this problem with a combination of:
Split the dataset generation entry points so each intent is generated separately (will use less memory).
Increase the nodejs heap memory size reference. Since Node 8, just setting an environmental variable will overwrite the heap max size. e.g.: export NODE_OPTIONS=--max_old_space_size=4096
Hope that helps
Hi,
I got following issues, please advise this.
[54060:0x2e79e10] 85032 ms: Mark-sweep 2019.6 (2024.1) -> 2019.6 (2024.1) MB, 1385.8 / 0.0 ms (average mu = 0.426, current mu = 0.000) last resort GC in old space requested [54060:0x2e79e10] 86623 ms: Mark-sweep 2019.6 (2024.1) -> 2019.6 (2024.1) MB, 1591.3 / 0.0 ms (average mu = 0.251, current mu = 0.000) last resort GC in old space requested
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x176a3fbc08a1
1: / anonymous /(aka / anonymous /) [0x178ab1201179] [/home/chatito/.npm/_npx/54060/lib/node_modules/chatito/dist/main.js:~469] [pc=0x2dcb2edfd81c](this=0x0725d1d404a9 )
2: next [0x176a3fbe3651](this=0x178ab12010d9 )
3: / anonymous /(aka / anonymous /) [0x178ab1201271] [/home/chatito/.npm/_npx/54060/lib/node_modules/cha...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory