# Fatal error - memory issue but there is enough memory

**URL:** <https://discourse.nodered.org/t/fatal-error-memory-issue-but-there-is-enough-memory/11446>\
**Category:** General\
**Created:** [23 May 2019 07:07 UTC](https://discourse.nodered.org/t/fatal-error-memory-issue-but-there-is-enough-memory/11446 "2019-05-23T07:07:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![johanmeer](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@johanmeer](https://discourse.nodered.org/u/johanmeer)\
**Post date:** [23 May 2019 07:07 UTC](https://discourse.nodered.org/t/fatal-error-memory-issue-but-there-is-enough-memory/11446/1 "2019-05-23T07:07:14Z")

</div>

Hi, can anyone help me discover the reason of fatal-error on this part of the log:

And is there a way to automatically start node-red after a fatal-error? we use this as a school project for monitoring several spaces and do a research on the data, but this becomes a problem if there is for hours data missing.

Thanks!!

We use a simple MQTT node that receives this every 2 seconds:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/a/a70db71dd05b13bde368b45f0bb7d26a5b3b98cb.png)

And we use the buienradar node. interval 5 minutes.

It runs on a VPS with debian, 50GB SSD and 1GB memory

Statistics show that there is a large increase of HDD and CPU usages starting on 4:42, the fatal error is on 5:41

FATAL ERROR: Committing semi space failed. Allocation failed - process out of memory  
1: node::Abort() [node-red]  
2: 0x8cd14c [node-red]  
3: v8::Utils::ReportOOMFailure(char const\*, bool) [node-red]  
4: v8::internal::V8::FatalProcessOutOfMemory(char const\*, bool) [node-red]  
5:  
v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector,  
v8::GCCallbackFlags) [node-red]  
6: v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace,  
v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node-red]  
7: v8::internal:🏭:NewFillerObject(int, bool,  
v8::internal::AllocationSpace) [node-red]  
8: v8::internal::Runtime\_AllocateInNewSpace(int,  
v8::internal::Object\*\*, v8::internal::Isolate\*) [node-red]  
9: 0x2349e67042fd  
Afgebroken

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [23 May 2019 08:09 UTC](https://discourse.nodered.org/t/fatal-error-memory-issue-but-there-is-enough-memory/11446/2 "2019-05-23T08:09:32Z")

</div>

So your are still having memory problems like your "solved" post...

> [@Fatal error: commiting semi space failed. Node-red stops](https://discourse.nodered.org/t/fatal-error-commiting-semi-space-failed-node-red-stops/11272):
>
> I have an ESP8266 that sends data from the DHT22 sensor to node-red via MQTT. I have also installed the buienradar node. Node-red stopped last 2 nights. In the log I first see these lines 6x in a time of 10 minutes: 18 May 01:19:34 - [error] [influxdb out: af18d328.370628] Error: No host available 18 May 01:20:17 - [info] [mqtt-broker: c156527e.9bbc] Disconnected from broker: mqtt: // localhost: 58073 18 May 01:20:24 - [info] [rain radar: 90709958.14d448] Failed: Error: socket hang up 18 Ma…

You may have temporarily masked the problem by changing poll rate to 5 seconds but an underlying issue exists.

As I said in the previous post, it looks like xpath module inside that node is being overwhelmed. Raise an issue with the author of that node.

---

<div class="post-metadata">

**Author:** ![johanmeer](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@johanmeer](https://discourse.nodered.org/u/johanmeer)\
**Post date:** [23 May 2019 08:24 UTC](https://discourse.nodered.org/t/fatal-error-memory-issue-but-there-is-enough-memory/11446/3 "2019-05-23T08:24:13Z")

</div>

Thanks, i did'nt see the buienradar node on the error\_log like on the other post. so i thought that is not causing the problem but something else is causing it. I already did raised an issue.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [23 May 2019 08:32 UTC](https://discourse.nodered.org/t/fatal-error-memory-issue-but-there-is-enough-memory/11446/4 "2019-05-23T08:32:09Z")

</div>

Maybe worth exploring an alternative weather node.

[https://flows.nodered.org/?term=weather&type=node&num\_pages=1](https://flows.nodered.org/?term=weather&type=node&num_pages=1)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [23 May 2019 18:58 UTC](https://discourse.nodered.org/t/fatal-error-memory-issue-but-there-is-enough-memory/11446/5 "2019-05-23T18:58:11Z")

</div>

> [@johanmeer](#):
>
> the buienradar node. interval 5 minutes.

Have you checked how often their data is really updated? I can't read the language I'm afraid. Most weather API's update hourly or even less. So you may be creating an issue for yourself.

Also, without seeing the flow, we can't tell what else is going on.

Getting an OOM error on that spec certainly seems to indicate some kind of serious memory allocation happening faster than the GC can cope with.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [15 April 2022 21:45 UTC](https://discourse.nodered.org/t/fatal-error-memory-issue-but-there-is-enough-memory/11446/6 "2022-04-15T21:45:25Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.