-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node-RED crashes when Postgres terminates connection unexpectedly due to out of memory error #97
Comments
Sorry for the delay. I will try to have a look to see if we can add more catches. |
If you are still around, would you be able to test this little patch? |
I built our docker container from the commit for that patch and yes it works :) I tested by causing the postgres instance to run out of memory with an infinite loop. |
Excellent, thanks for the quick feedback @marcus-clements 👍🏻 |
@Alkarex Unfortunately this error has occurred again in v0.15.1, but with a different line number in I am experimenting with connection pool settings. The change that causes this error to not be handled again seems to be that I added an Application Name in the Connection pool settings and set the idle timeout to 10s.
Is there some way to configure Node-RED to give the call stack so I can help you add further catches? |
@Alkarex do you want to reopen this issue or should I create a new one? |
Let's reopen here. I do not know the answer to your question. Additional help welcome. I will try to find time to look at it but I am swamped until at least the weekend. |
This looks related to #50
Node-RED v14.2
node.js v22.11.0
I am executing a query that occasionally causes an out of memory error in Postgres. This throws an uncaught exception which crashes Node-RED
The text was updated successfully, but these errors were encountered: