最近，在我的一个项目中遇到了同样的问题。尝试了一些事情，任何人都可以尝试调试以确定根本原因:

正如每个人建议的那样，通过添加以下命令来增加节点的内存限制: ｛ "脚本":{ "server":"node——max-old-space-size={size-value} server/index.js" ｝ ｝

这里size-value我已经为我的应用程序定义了1536(因为我的kubernetes pod内存是2 GB的限制，请求1.5 GB)

因此，始终根据前端基础设施/架构限制(略小于限制)定义size-value。

在上面的命令中，使用——max-old-space-size命令在node之后，而不是文件名server/index.js之后。

If you have ngnix config file then check following things: worker_connections: 16384 (for heavy frontend applications) [nginx default is 512 connections per worker, which is too low for modern applications] use: epoll (efficient method) [nginx supports a variety of connection processing methods] http: add following things to free your worker from getting busy in handling some unwanted task. (client_body_timeout , reset_timeout_connection , client_header_timeout,keepalive_timeout ,send_timeout). Remove all logging/tracking tools like APM , Kafka , UTM tracking, Prerender (SEO) etc middlewares or turn off. Now code level debugging: In your main server file , remove unwanted console.log which is just printing a message. Now check for every server route i.e app.get() , app.post() ... below scenarios:

Data => if(Data) res.send(Data) //你真的需要等待数据或API返回一些我必须等待的响应吗??，如果不是这样修改:

data => res.send(data) // this will not block your thread, apply everywhere where it's needed

else part: if there is no error coming then simply return res.send({}) , NO console.log here. error part: some people define as error or err which creates confusion and mistakes. like this: `error => { next(err) } // here err is undefined` `err => {next(error) } // here error is undefined` `app.get(API , (re,res) =>{ error => next(error) // here next is not defined })` remove winston , elastic-epm-node other unused libraries using npx depcheck command. In the axios service file , check the methods and logging properly or not like : if(successCB) console.log("success") successCB(response.data) // here it's wrong statement, because on success you are just logging and then `successCB` sending outside the if block which return in failure case also. Save yourself from using stringify , parse etc on accessive large dataset. (which i can see in your above shown logs too.

最后但并非最不重要的是，每当应用程序崩溃或pod重新启动时，都要检查日志。在日志中特别查找这部分:安全上下文 这将告诉你为什么，在哪里，谁是背后的崩溃的罪魁祸首。

我在AWS Elastic Beanstalk上有这个错误，从t3升级实例类型。micro(免费层)到t3。小修正错误

如果你想更改节点(windows)的全局内存，请进入高级系统设置->环境变量->新用户变量

variable name = NODE_OPTIONS
variable value = --max-old-space-size=4096

你可以通过以下方法修复Node.js中的“堆出内存”错误。

Increase the amount of memory allocated to the Node.js process by using the --max-old-space-size flag when starting the application. For example, you can increase the limit to 4GB by running node --max-old-space-size=4096 index.js. Use a memory leak detection tool, such as the Node.js heap dump module, to identify and fix memory leaks in your application. You can also use the node inspector and use chrome://inspect to check memory usage. Optimize your code to reduce the amount of memory needed. This might involve reducing the size of data structures, reusing objects instead of creating new ones, or using more efficient algorithms. Use a garbage collector (GC) algorithm to manage memory automatically. Node.js uses the V8 engine's garbage collector by default, but you can also use other GC algorithms such as the Garbage Collection in Node.js Use a containerization technology like Docker which limits the amount of memory available to the container. Use a process manager like pm2 which allows to automatically restart the node application if it goes out of memory.

我将提到两种解决方案。

我的解决方案:在我的例子中，我将这个添加到我的环境变量:

export NODE_OPTIONS=--max_old_space_size=20480

但是即使我重新启动我的电脑，它仍然不能工作。我的项目文件夹在d:\ disk。所以我把我的项目移到c:\ disk，它工作了。

我队友的解决方案是:打包。Json配置也工作。

"start": "rimraf ./build && react-scripts --expose-gc --max_old_space_size=4096 start",

如果我没记错的话，V8的内存使用有一个严格的标准限制，大约是1.7 GB，如果你不手动增加它的话。

在我们的一个产品中，我们在部署脚本中遵循了这个解决方案:

 node --max-old-space-size=4096 yourFile.js

还会有一个新的空间命令，但正如我在这里读到的:a-tour-of-v8-garbage-collection，新空间只收集新创建的短期数据，旧空间包含所有引用的数据结构，这应该是您的情况下的最佳选择。