3 ms·
Not too long ago I've written some simple CAPTCHA service with Node.js, node-redis and node-canvas. It was a simple application that generated a word from a spe
by drdaeman 16y ago
Not too long ago I've written some simple CAPTCHA service with Node.js, node-redis and node-canvas. It was a simple application that generated a word from a specific grammar, saved it to Redis for further reference and returned a PNG.
While being ridiculously fast it leaked memory like crazy. So I've found that there were almost no debugging tools (except for old good gdb) to find out what was going on. (I've heard that there are some changes like `node debug`, though. Should dig the archives and try code with latest Node version.)
I believe this was an inherent consequence of JavaScript and V8 being tailored to short-lifetime (milliseconds of DOM operations, then lazy waiting for events to fire) applications with low amount of events (user in-browser activity).
- jrockway 16y agoI believe this was an inherent consequence of JavaScript and V8 being tailored to short-lifetime (milliseconds of DOM operations, then lazy waiting for events to fire) applications with low amount of events (user in-browser activity). Nope, it's just bugs. Every programming language has memory-related bugs... just less of them as they get older.