# Node-red-node-google - node-red crash

**URL:** <https://discourse.nodered.org/t/node-red-node-google-node-red-crash/10096>\
**Category:** General\
**Created:** [13 April 2019 09:47 UTC](https://discourse.nodered.org/t/node-red-node-google-node-red-crash/10096 "2019-04-13T09:47:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Baggerfahrer](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@Baggerfahrer](https://discourse.nodered.org/u/Baggerfahrer)\
**Post date:** [13 April 2019 09:47 UTC](https://discourse.nodered.org/t/node-red-node-google-node-red-crash/10096/1 "2019-04-13T09:47:20Z")

</div>

Hi all.

I got a question concerning the google "node-red-node-google" node. see here: [Link](https://flows.nodered.org/node/node-red-node-google)

I would like to get a telegram push message everytime there is a entry in my google calendar. So I use the above mentioned node and configured it accordlingly. But the strange this is now, that when i would like to deploy, my node red service crashes.

See here my flow:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/6/6617d66950b57c228bc050dbc1d1fd8e7548882c.png)

Now, when i would deploy this, my node red crases and it is heavily difficult to set it up again. Node-red log says this:

> \<--- Last few GCs ---\>  
> [1723:0x39baab8] 49240 ms: Mark-sweep 260.3 (272.0) -\> 260.2 (273.0) MB, 2100.5 / 0.1 ms (average mu = 0.186, current mu = 0.021) allocation failure scavenge might not succeed  
> [1723:0x39baab8] 51752 ms: Mark-sweep 261.3 (273.0) -\> 261.2 (273.5) MB, 2494.6 / 0.1 ms (average mu = 0.092, current mu = 0.007) 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  
> nodered.service: Main process exited, code=killed, status=6/ABRT  
> nodered.service: Unit entered failed state.  
> nodered.service: Failed with result 'signal'.  
> nodered.service: Service hold-off time over, scheduling restart.

Any ideas? many thanks!

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [13 April 2019 10:08 UTC](https://discourse.nodered.org/t/node-red-node-google-node-red-crash/10096/2 "2019-04-13T10:08:54Z")

</div>

what versions of node-red nodejs are you using?

---

<div class="post-metadata">

**Author:** ![Baggerfahrer](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@Baggerfahrer](https://discourse.nodered.org/u/Baggerfahrer)\
**Post date:** [13 April 2019 16:22 UTC](https://discourse.nodered.org/t/node-red-node-google-node-red-crash/10096/3 "2019-04-13T16:22:56Z")

</div>

node red: Version 0.19.5  
node --version gives me v10.15.3

I use it with openhabian distribution

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [13 April 2019 19:09 UTC](https://discourse.nodered.org/t/node-red-node-google-node-red-crash/10096/4 "2019-04-13T19:09:28Z")

</div>

What makes you sure it’s the Google node that’s doing this?

How is your inject node configured?

If you split your flow so it is  
[inject]—-[google]—-[debug]. does it still happen?

---

<div class="post-metadata">

**Author:** ![Baggerfahrer](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@Baggerfahrer](https://discourse.nodered.org/u/Baggerfahrer)\
**Post date:** [18 April 2019 07:21 UTC](https://discourse.nodered.org/t/node-red-node-google-node-red-crash/10096/5 "2019-04-18T07:21:44Z")

</div>

you were right, the system works properly. i changed the setting accordingly to your comment and it works like a charm.

meaning there was propably a mistake anywhere in my flow, i assume in the change node

many thanks!
