How to diagnose Segmentation Fault on Node.Js -
my node.js application fails "segmentation fault" , @ loss how diagnose cause. mentioned below have dramatically reduced frequency raising maxlisteners not made problem go away.
the application runs on beaglebone black under node v0.8.22 , uses socket.io communicate realtime data browser pages displayed on bbb's lcd display. collects data sensor connected via i2c using korevec/node-i2c library. have, however, isolated library , still have failures.
the failures occur when have streamed data while client though occasionally/rarely happen @ other times well. not surprising app uses socket.io communicate on pages streaming page @ higher volume.
i getting below message:
(node) warning: possible eventemitter memory leak detected. 11 listeners added. use emitter.setmaxlisteners() increase limit.
trace
and have been doing since day 1. seeing symptoms of memory leak since raised maxlisteners memory usage stays constant. failure rate after making change went down dramatically has not gone away completely. using socket.io on top of http , raised maxlisteners both socket.it , http.
how 1 go diagnosing problem? memory leak error related? can post code there quite bit of , not sure parts relevant.
thanks help, cheers,
Comments
Post a Comment