-
Notifications
You must be signed in to change notification settings - Fork 2
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
Possible memory leak? #61
Comments
|
|
Thoughts:May be backend realted?!
Perhaps the backed is not signaling correctly a broken/collapsed bridged. A simple repl proceess alone starts 15 node processes:
2 before issuing |
|
Added some debug messages in the backend to see if the ws is closed properly:
In class.interface.js |
"Websocket is dead": But no debug message ">> stream fired "end" event in router.api.devices.js" is printed. .178 is the lowboard custom LED Strip. |
Turning on/off the raspberry, leads to broken websocket connection. Is this a issue in the plugin, backend or connector. The backend/connector should handle that edge case. |
This could be a wider problem that thought. I think the backend should handle this and terminate the websocket connection between connector & backend, when no data is transmitted for a certain time. |
Local "production" system produces OOM, killing the connector:
valgrind
heaptrack
The text was updated successfully, but these errors were encountered: