Howard Hellyer

This looks like an interaction with the signal handler used for creating a heapdump. I can reproduce it without appmetrics by running with the heapdump module which appmetrics-dash includes: `>...

@Aerex - Does setting `NODE_HEAPDUMP_OPTIONS` (see above) fix the problem for you?

Having had a local discussion about this I think the concern was that clang-format wouldn't be available when running citgm builds. (I'd be happy with something that a developer just...

This looks good and I think we should merge it in but I have one major issue and one minor one. The main issue is this only checks the .js...

The MacOS builds of lldb can open Linux core dumps without any problems, provided you point it at the right Linux binary. It's how I do a lot of my...

I agree it's probably not possible to tell which objects are leaking from one dump. Memory Analyzer for Java (http://www.eclipse.org/mat/) generates a dominator tree which shows you which references are...

@bnoordhuis - I don't think the two are quite the same the dominator tree algorithm works out which object is responsible for keeping that retained space alive. Memory Analyzer shows...

I think the moving the project under Node.js would be great, it would probably improve the visibility and hopefully adoption and participation as well. I'm not sure I know enough...

I think it's only in the 4.0 branch. (There's a github mirror of the llvm project that's easier to search, I checked one of the files I updated here: https://github.com/llvm-mirror/lldb/blob/release_40/source/Plugins/Process/elf-core/ThreadElfCore.h)...

In an ELF core (linux) you might be able to use the program headers or the NT_FILE note to validate you are using the right executable but you'd probably want...