Conditional jump or move depends on uninitialised value(s) about node-memwatch

[lloyd]

please report your node version and more specific steps to reproduce - like minimal javascript code to reproduce the problem? Here's my attempt:

$ valgrind node node_modules/.bin/mocha tests
==6719== Memcheck, a memory error detector
==6719== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==6719== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==6719== Command: node node_modules/.bin/mocha tests
==6719== 
==6719== Warning: noted but unhandled ioctl 0x5451 with no size/direction hints
==6719==    This could cause spurious value errors to appear.
==6719==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
==6719== Warning: noted but unhandled ioctl 0x5451 with no size/direction hints
==6719==    This could cause spurious value errors to appear.
==6719==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
==6719== Warning: noted but unhandled ioctl 0x5451 with no size/direction hints
==6719==    This could cause spurious value errors to appear.
==6719==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
==6719== Warning: set address range perms: large range [0x26c583d5a000, 0x26c5a3d5a000) (noaccess)
==6724== Warning: invalid file descriptor -1 in syscall close()
==6724== Warning: invalid file descriptor -1 in syscall close()
==6724== Warning: invalid file descriptor -1 in syscall close()

  ....

  ✔ 4 tests complete (246ms)

==6719== 
==6719== HEAP SUMMARY:
==6719==     in use at exit: 949,582 bytes in 214 blocks
==6719==   total heap usage: 2,100 allocs, 1,886 frees, 10,729,889 bytes allocated
==6719== 
==6719== LEAK SUMMARY:
==6719==    definitely lost: 0 bytes in 0 blocks
==6719==    indirectly lost: 0 bytes in 0 blocks
==6719==      possibly lost: 496 bytes in 3 blocks
==6719==    still reachable: 949,086 bytes in 211 blocks
==6719==         suppressed: 0 bytes in 0 blocks
==6719== Rerun with --leak-check=full to see details of leaked memory
==6719== 
==6719== For counts of detected and suppressed errors, rerun with: -v
==6719== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)

[lloyd]

(closing for now, please re-open with specifics)

[strk]

Sorry I completely forgot how I obtained that. It was likely with adding snapshot taking commands without preventing the GC run loop (as the documentation said it would have been safe to do).

But keep closed, I'll open again when able to reproduce.