nodejs一次内存溢出定位和解决方案

公司电脑增加内存到28G后，项目运行npm run dev:test总是在修改生效后热更新阶段出现JavaScript heap out of memory，没加内存前，顶多是跑不动，增加内存了，动不动就终止进程，启动阶段页面。

下面是控制台输出

ruby 复制代码

95% emitting CopyPlugin
<--- Last few GCs --->

[23456:00000191F6233FD0]   248918 ms: Mark-sweep 3938.0 (4134.7) -> 3936.5 (4129.6) MB, 956.7 / 0.1 ms  (average mu = 0.121, current mu = 0.003) allocation failure scavenge might not succeed[23456:00000191F6233FD0]   250058 ms: Mark-sweep 3942.0 (4134.6) -> 3936.5 (4126.1) MB, 1129.1 / 0.1 ms  (average mu = 0.072, current mu = 0.009) allocation failure scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF7C6CD61BF napi_wrap+133519
 2: 00007FF7C6C6F6D6 DSA_meth_get_flags+63062
 3: 00007FF7C6C7056D node::OnFatalError+301
 4: 00007FF7C755599E v8::Isolate::ReportExternalAllocationLimitReached+94     
 5: 00007FF7C753A78D v8::SharedArrayBuffer::Externalize+781
 6: 00007FF7C73E3F8C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1516
 7: 00007FF7C73EF3AA v8::internal::Heap::ProtectUnprotectedMemoryChunks+1258  
 8: 00007FF7C73EC4E9 v8::internal::Heap::PageFlagsAreConsistent+2457
 9: 00007FF7C73E1081 v8::internal::Heap::CollectGarbage+2049
10: 00007FF7C73DF285 v8::internal::Heap::AllocateExternalBackingStore+1349
11: 00007FF7C73F9115 v8::internal::GCIdleTimeHandler::ShouldDoContextDisposalMarkCompact+1029
12: 00007FF7C73F9565 v8::internal::Factory::AllocateRaw+37
13: 00007FF7C740DBDF v8::internal::FactoryBase<v8::internal::Factory>::NewRawTwoByteString+79
14: 00007FF7C7201169 v8::internal::String::SlowFlatten+441
15: 00007FF7C70AFCD0 unibrow::Utf8::EncodeOneByte+656
16: 00007FF7C7561426 v8::String::Utf8Length+22
17: 00007FF7C6C8F497 v8::internal::Malloced::operator delete+21831
18: 00007FF7C750299F v8::internal::Builtins::builtin_handle+322591
19: 00007FF7C7501F34 v8::internal::Builtins::builtin_handle+319924
20: 00007FF7C7502228 v8::internal::Builtins::builtin_handle+320680
21: 00007FF7C7502073 v8::internal::Builtins::builtin_handle+320243
22: 00007FF7C75E0EAD v8::internal::SetupIsolateDelegate::SetupHeap+474477
23: 000000CB5D2A2B9E 
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! [email protected] dev:test: `cross-env NODE_ENV=development PACKAGE_TYPE=service vue-cli-service serve --mode test`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the [email protected] dev:test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\pe7er\AppData\Roaming\npm-cache\_logs\2024-03-12T07_03_18_962Z-debug.log

具体错误日志

css 复制代码

0 info it worked if it ends with ok
1 verbose cli [1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',1 verbose cli   'run',1 verbose cli   'dev:test'1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predev:test', 'dev:test', 'postdev:test' ]
5 info lifecycle [email protected]~predev:test: [email protected]
6 info lifecycle [email protected]~dev:test: [email protected]
7 verbose lifecycle [email protected]~dev:test: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~dev:test: PATH: C:\Users\pe7er\AppData\Roaming\nvm\v14.21.3\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\pe7er\Documents\Developer\gitlab\xxx-h5-web-next\node_modules\.bin;C:\Users\pe7er\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\pe7er\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Users\pe7er\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Program Files\SourceGear\Common\DiffMerge;C:\Users\pe7er\.console-ninja\.bin;C:\Users\pe7er\AppData\Local\Microsoft\WindowsApps;C:\Users\pe7er\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\pe7er\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\pe7er\AppData\Local\JetBrains\Toolbox\scripts;C:\Users\pe7er\.deno\bin;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle [email protected]~dev:test: CWD: C:\Users\pe7er\Documents\Developer\gitlab\xxx-h5-web-next
10 silly lifecycle [email protected]~dev:test: Args: [
10 silly lifecycle   '/d /s /c',
10 silly lifecycle   'cross-env NODE_ENV=development PACKAGE_TYPE=service vue-cli-service serve --mode test'
10 silly lifecycle ]
11 silly lifecycle [email protected]~dev:test: Returned: code: 134  signal: null
12 info lifecycle [email protected]~dev:test: Failed to exec dev:test script
13 verbose stack Error: [email protected] dev:test: `cross-env NODE_ENV=development PACKAGE_TYPE=service vue-cli-service serve --mode test`
13 verbose stack Exit status 134
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\pe7er\AppData\Roaming\nvm\v14.21.3\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:400:28)
13 verbose stack     at ChildProcess.<anonymous> (C:\Users\pe7er\AppData\Roaming\nvm\v14.21.3\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:400:28)
13 verbose stack     at maybeClose (internal/child_process.js:1088:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:296:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\Users\pe7er\Documents\Developer\gitlab\xxx-h5-web-next
16 verbose Windows_NT 10.0.19044
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev:test"
18 verbose node v14.21.3
19 verbose npm  v6.14.18
20 error code ELIFECYCLE
21 error errno 134
22 error [email protected] dev:test: `cross-env NODE_ENV=development PACKAGE_TYPE=service vue-cli-service serve --mode test`
22 error Exit status 134
23 error Failed at the [email protected] dev:test script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 134, true ]

看起来眼睛痛，但其实关键的信息就两句

allocation failure scavenge might not succeed(分配失败清除程序可能不会成功)
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory致命错误:无效的标记压缩接近堆限制分配失败- JavaScript堆内存不足

增加node的max_old_space_size即可，"旧空间"是 V8 托管（也称为垃圾收集）堆（即 JavaScript 对象所在的位置）中最大和最可配置的部分，并且 --max-old-space-size 标志控制其最大大小。随着内存消耗接近极限，V8 将花费更多时间在垃圾收集上，以释放未使用的内存。

加多少合适呢，可以参考下面的文档。

参考文档：

nodejs.cn/api/cli.htm...

stackoverflow.com/questions/4...

没加内存前的默认配置

tip：退出使用.exit

widnow可以打开一个cmd或shell，一般你用什么终端启动项目，就在哪个终端里执行下面的命令，如果使用gitbash，则需要用下面的linux/unix的命令。我的电脑内存比较富裕，直接给最大10g，但实际上给大一些，内存也没有满过，V8的GC（内存垃圾回收）还是很强的。

shell 复制代码

setx NODE_OPTIONS --max_old_space_size=10240

按照上面的方法设置后，不仅项目启动速度变快了，热更新时再也没有因为垃圾回收内存不够造成项目中断的情况了，问题解决。

扩展

linux/unix可以打开一个zsh、shell里执行

shell 复制代码

export NODE_OPTIONS="--max_old_space_size=10240"

当然也可以直接使用node

shell 复制代码

$ node --max-old-space-size=8192 index.js

也可以在当前项目中设置

json 复制代码

{
  "scripts": {
    "dev:test": "node --max-old-space-size=8192 其他命令"
  }
}

可以使用cross-env来抹平系统差异

json 复制代码

{
  "scripts": {
    "dev:test": "cross-env NODE_OPTIONS=--max-old-space-size=8192 其他命令"
  }
}