I can't put my finger on exactly when this condition started happening. Sometime in the last two weeks or so. When I click deploy, about 75% of the time, the first try fails and I have to click deploy again. I experience this condition when i try to deploy both Full and Modified flows. When the f…

Error processing windowTypes: This property is deprecated [global.min.js:250](moz-extension://b7d0005b-5048-f541-8ddc-26fdb5b79842/global.min.js) makeError resource://gre/modules/Schemas.jsm:459 logDeprecation resource://gre/modules/Schemas.jsm:1109 checkDeprecated resource://gre/modules/Schemas.…

The browser console contents for the event above and a second consecutive failure: Error processing windowTypes: This property is deprecated [global.min.js:250](moz-extension://b7d0005b-5048-f541-8ddc-26fdb5b79842/global.min.js) makeError resource://gre/modules/Schemas.jsm:459 logDeprecation reso…

That error is coming from some extension you have installed in the browser. It is not node-red.

Thanks for the quick response! I didn't think to look in the browser console. I only have two extensions: 1Password and Cisco Webex. Both are now disabled and it seems to have made a difference.

[image] athome: Cisco Webex I would look to that being the culprit initially. Depending on what version you are using. I always keep it turned off and only turn in on when I have to use the c**ppy service from CISCO. I use the "SimpleExtManage" Chrome extension to be able to turn on/off exten…

This week's sprint is going to be dedicated to resolving this condition, which still persists. However, I am certain that I don't know where to start in the diagnosis. I have read a few posts to which some of you have contributed related to JavaScript heap out of memory and they are pretty CSI-lik…

Is it possible that having too many sequences and/or too many nodes in a flow could cause the JavaScript heap overflow? My irrigation flow is my largest. I have disabled this flow to test to see if it makes a difference. I have posted it here. Well, maybe not. The flow export is 185K characters…

My irrigation flow had 277 nodes. I have just made a change that resulted in a reduction by 55. This change has made a dramatic improvement in the behavior. I have been able to Deploy without incident after making this change.

For reference, my live flow file is 626k (1025 nodes). -rw-r--r-- 1 pi pi 626K Jun 15 13:19 flows.json Oddly, my secondary instance isn't much smaller though it has a lot less in it - 409k (655 nodes). I have no problems with either.

TotallyInformation, Thanks for the reference. The numbers i quoted above (185k and 277 nodes) were for the contents of a single flow tab. My flows file is 851,289. How did you count the nodes across all tabs? That would be useful to know how to do.

Node-RED

Node-RED Forum

Deploy requires more than one attempt

General

ukmoose 21 June 2019 12:32 13

Topic		Replies	Views
Deploy "Hangs" all of a sudden General	13	923	14 January 2022
Deploy button doesn't click General	26	2866	22 September 2019
Deploy failing. No response from server General	36	9759	25 January 2024
Deploy button not working General	39	5623	3 February 2021
Node-red crashes after a while and no html view -- please help -- SOLVED General	15	4977	28 September 2021

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Deploy requires more than one attempt

Related topics