Anna Henningsen

Hm, is there anything specific I can provide to this discussion? Overall I’m still somewhat unsure about the general approach, and I don’t see anywhere where suggestions for API or...

@benjamingr I think a full core dump might be nice for a report. Also, just curious, what makes you think this is related to async_hooks? (Also, I can’t reproduce locally...

> OK -- the bisect seems to be implicating this commit as the one that introduced this segmentation fault. nodejs/node@56530f0 @astormnewrelic Are you sure? That commit doesn’t seem suitable to...

@astormnewrelic I think that leaves two main options: - This isn’t related to async hooks, and something else happened between bluebird 3.5 and 3.6 that affected this, or (and I...

@benjamingr That still shouldn’t be an issue, right? Like, if calling `timer.refresh()` makes the process crash, that’s not “just” a bluebird issue? Sadly, those verbose valgrind warnings correspond to a...

> Right, this still looks like a bug in core and I am still not sure why it happens. Why would OpenSSL even be related to `timer.refresh()` causing a segfault?...

@astormnewrelic When working with custom builds, the binary used for causing the crash is just as much needed for debugging as the core dump itself :)

@astormnewrelic As far as I know, the core dump doesn’t contain symbols, which are necessary to figure out what code actually corresponds to which functions in the original binary. I...

From a first look, it seems like the libuv timer heap has one entry, but that refers to a null pointer; that seems wrong, but it’s not obvious to me...

@astorm I’m running Ubuntu 18.04, with Linux 4.15.0-65-generic on x64… and there’s nothing really special about my setup, I think