首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >Node-red内存不足问题

Node-red内存不足问题
EN

Stack Overflow用户
提问于 2019-03-05 05:55:02
回答 2查看 2K关注 0票数 0

我在node-red安装中使用了这个文档(Node-red doc for RPI)。安装工作进行得很好。但在启动node-red-startnode-red-pi之后,我看到下一个出现错误的日志。我不是nodejs专家。日志中为npm和nodejs版本。

代码语言:javascript
复制
Mar 22:48:23 - [info] 

Welcome to Node-RED
===================

4 Mar 22:48:23 - [info] Node-RED version: v0.19.6
4 Mar 22:48:23 - [info] Node.js  version: v10.15.2
4 Mar 22:48:23 - [info] Linux 4.9.35-v7+ arm LE
4 Mar 22:48:25 - [info] Loading palette nodes
4 Mar 22:48:30 - [info] Worldmap version 1.5.29
4 Mar 22:48:31 - [info] Dashboard version 2.14.0 started at /ui
4 Mar 22:48:35 - [warn] ------------------------------------------------------
4 Mar 22:48:35 - [warn] [node-red-contrib-generic-ble/generic-ble] Error: Cannot find module 'bluetooth-hci-socket'
4 Mar 22:48:35 - [warn] ------------------------------------------------------
4 Mar 22:48:35 - [info] Settings file  : /home/pi/.node-red/settings.js
4 Mar 22:48:35 - [info] Context store  : 'default' [module=memory]
4 Mar 22:48:35 - [info] User directory : /home/pi/.node-red
4 Mar 22:48:35 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Mar 22:48:35 - [info] Flows file     : /home/pi/.node-red/flows_server.json
4 Mar 22:48:35 - [info] Server now running at https://127.0.0.1:1880/
4 Mar 22:48:35 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

4 Mar 22:48:35 - [info] Starting flows
4 Mar 22:48:37 - [info] [worldmap:1ac45205.ff98ee] started at /worldmap
4 Mar 22:48:37 - [info] [worldmap:ac8fa4a4.314918] started at /worldmap
4 Mar 22:48:38 - [info] [worldmap:20c6db58.a44e34] started at /worldmap
4 Mar 22:48:38 - [info] [worldmap:bf26442c.e7f3b8] started at /worldmap
4 Mar 22:48:38 - [info] [worldmap:ee74d5bc.e8f268] started at /worldmap
4 Mar 22:48:38 - [info] Started flows
4 Mar 22:48:38 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://localhost:1883

<--- Last few GCs --->

[24581:0x34f1a28]   138171 ms: Mark-sweep 702.7 (729.7) -> 702.7 (733.2) MB, 9657.7 / 0.1 ms  (average mu = 0.092, current mu = 0.004) allocation failure scavenge might not succeed
[24581:0x34f1a28]   148339 ms: Mark-sweep 706.3 (733.2) -> 706.3 (733.2) MB, 9979.6 / 0.1 ms  (average mu = 0.055, current mu = 0.019) allocation failure scavenge might not succeed


<--- JS stacktrace --->
Cannot get stack trace in GC.
FATAL ERROR: MarkCompactCollector: semi-space copy, fallback in old gen Allocation failed - JavaScript heap out of memory

现在我有了更多可用的信息,堆栈跟踪...

代码语言:javascript
复制
==== JS stack trace =========================================

    0: ExitFrame [pc: 0x37deae9c]
    1: StubFrame [pc: 0x37dec080]
Security context: 0x4b492701 <JSObject>
    2: encode(aka encode) [0x4fdd867d] [/home/pi/.node-red/node_modules/qs/lib/utils.js:~118] [pc=0x20067594](this=0x36c8438d <undefined>,str=0x43a423d1 <Very long string[17508]>)
    3: arguments adaptor frame: 2->1
    4: stringify(aka stringify) [0x4fdd737d] [/home/pi/.node-red/node_modules/qs/lib/stringify.js:61] [bytecode=0x289...

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

这意味着在我的节点中是有错误的节点?如果是,我如何找出哪个节点出错?

EN

回答 2

Stack Overflow用户

回答已采纳

发布于 2019-03-07 05:54:23

问题出在错误的电报节点配置中。这在qs/lib/utils.js:~118中调用了self字符串更大,直到堆空间...

Thx

票数 0
EN

Stack Overflow用户

发布于 2019-03-05 17:20:17

错误的重要部分是:

代码语言:javascript
复制
 fallback in old gen Allocation failed - JavaScript heap out of memory

这意味着运行Node-RED的NodeJS虚拟机已耗尽内存。

如果不能正确理解你的流在做什么,就不可能说出为什么会发生这种情况,但一个合理的猜测是,你要么试图处理传入的消息(来自某处),速度比它们到达的速度慢,要么可能你在上下文中存储了一些东西,并且永远不会移除它们,所以它们会随着时间的推移而积累起来。

编辑:

OOM的堆栈跟踪不一定有帮助,这只是在没有更多空间的瞬间尝试分配的内容。这并不意味着它就是原因。

正如前面提到的,调试它的唯一方法是详细了解您的流正在做什么(而Stack Overflow可能不是解决此问题的最佳位置。你可能会在Node-RED论坛或slack上做得更好,在那里你可能会找到可以与你共事的人)

票数 2
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/54992141

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档