node-nanomsg: memory leak
PollSendSocket leaks. At least valgrind thinks so.
==4428== 2,112 bytes in 12 blocks are possibly lost in loss record 996 of 1,041
==4428== at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4428== by 0x985CF78: PollSendSocket(Nan::FunctionCallbackInfo<v8::Value> const&) (in /home/reqshark/node_modules/nanomsg/build/Release/node_nanomsg.node)
==4428== by 0x985C555: Nan::imp::FunctionCallbackWrapper(v8::FunctionCallbackInfo<v8::Value> const&) (in /home/reqshark/node_modules/nanomsg/build/Release/node_nanomsg.node)
==4428== by 0x913C21: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) (in /home/reqshark/.nvm/versions/node/v5.6.0/bin/node)
==4428== by 0x93E100: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>&) (in /home/reqshark/.nvm/versions/node/v5.6.0/bin/node)
==4428== by 0x93E5F1: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) (in /home/reqshark/.nvm/versions/node/v5.6.0/bin/node)
==4428== by 0x1D5F9040839A: ???
==4428== by 0x1D5F90644AB0: ???
==4428== by 0x1D5F906448B7: ???
==4428== by 0x1D5F90408296: ???
==4428== by 0x1D5F9063F5EA: ???
==4428== by 0x1D5F9066B954: ???
cc: @nickdesaulniers, @kkoopa, @tcr
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 38 (22 by maintainers)
Commits related to this issue
- add asan build support #151 build with `npm i --asan=true`. This will use a build that links in asan at runtime. The odd split in .gyp files exists because we want to compile nanomsg with asan inst... — committed to nickdesaulniers/node-nanomsg by nickdesaulniers 8 years ago
- add asan build support #151 (PR #167) build with `npm i --asan=true`. This will use a build that links in asan at runtime. The odd split in .gyp files exists because we want to compile nanomsg ... — committed to nickdesaulniers/node-nanomsg by nickdesaulniers 8 years ago
Thanks for your code pointing to where the leaks were occurring. Thanks all, it’s good to get long standing issues resolved.