We certainly do performance tests, and we also don't auto-update. The issue here was it was a slow leak, so it took time and significant load for the pattern of errors to present itself.
Is anyone else getting a redirect loop when trying the link? At first I was thinking it had to do with my Firefox settings to force HTTPS but even just:
The site is broken right now, but I read this when it was first submitted some time ago.
Contrary to what the title would suggest, it's about finding a mundane JS memory leak in moment.js by attaching the chrome inspector to node. There's no out-of-the-ordinary tale here and there's certainly little mystery.
The article might be useful if you've never done it before and need some pointers.
9 comments
[ 4.8 ms ] story [ 38.3 ms ] threadcurl -L lukedeniston.com/memory-leak-mystery
> curl: (47) Maximum (50) redirects followed
isn't working.
Contrary to what the title would suggest, it's about finding a mundane JS memory leak in moment.js by attaching the chrome inspector to node. There's no out-of-the-ordinary tale here and there's certainly little mystery.
The article might be useful if you've never done it before and need some pointers.
Doesn't make sense. All child processes should get that env var.