Inspecting Electron's native stack to diagnose nightmare JavaScript memory leaks

I'm sure there's a better way of debugging "my Electron app ran out of memory during the night and I don't know why" - but this was a successful attempt to apply brute force to figure out why Element kept crashing.