Skip to content
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

nodejs segfaults on zwave.disconnect() #21

Open
bbf opened this issue Nov 28, 2013 · 0 comments
Open

nodejs segfaults on zwave.disconnect() #21

bbf opened this issue Nov 28, 2013 · 0 comments

Comments

@bbf
Copy link

bbf commented Nov 28, 2013

Hello,

I'm creating a Node-Red node for node-openzwave, and I have some listeners that run when the flows are starting and stopping. But the thing is that Node-Red sends a stop before sending the start event, and so I end up calling zwave.disconnect() before ever calling the connect. And that is causing zwave to segfault nodejs. For now I'll just use boolean to avoid that, but I don't think that node-openzwave should crash like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant