Node-red segmentation fault

RobbieClarken / node-epics

EPICS Channel Access for node.js

19 stars 10 forks source link

Node-red segmentation fault #7

Open swertz opened 4 years ago

swertz commented 4 years ago

Using this library (along with https://github.com/SandyLabs/node-red-contrib-epics/) results in a segmentation fault of node-red (v1.1.3) as soon as a flow including an "epics in" node is deployed.

Tested versions of epics-base are 3.14.12.18, 3.15.8, 7.0.4 and all yield the same behaviour. Running caget or caput in the CLI works fine.

elstanto commented 3 years ago

Hi, sorry I didn't spot this for some reason. Have you moved on or would you like me to have a look? I'm the author of the node-red node.

swertz commented 3 years ago

In the end we decided on another system (python backend using pyepics and MQTT messages for node-red <-> backend interfacing)...

But I wanted to report the bug in any case.

RobbieClarken commented 3 years ago

Thanks for reporting the bug @swertz . Unfortunately I don't work with EPICS anymore so I'm not really in a position to continue maintaining this project. For anyone looking to use EPICS from nodejs, this project looks promising: https://github.com/onichandame/epics-ioc-connection

elstanto commented 3 years ago

Thanks for the link @RobbieClarken. I'll port the node-red library over to that, looks good.