Tracking Down a Python Memory Leak

Re:Tracking Down a Python Memory Leak by partycoder on Wednesday December 07, 2016 @03:19PM (#13125845)

Reminds me of myself tracing a memory leak in a node app loading a core dump into an IllumOS VM with mdb_v8. Not so simple/friendly/happy after all.

(You could argue that you could generate a heap snapshot with v8-profiler but I was against time).

[ Parent | on HN ]

Re:Tracking Down a Python Memory Leak by bcantrill on Wednesday December 07, 2016 @04:46PM (#13126539)

Would be curious for detail on your experiences; we do this a lot (we developed mdb_v8) and we've continued to extend/develop mdb_v8 to make it easier -- but trying to debug node memory growth is not something I would every characterize as simple, friendly or happy (despite our best efforts).

[ Parent | on HN ]

Re:Tracking Down a Python Memory Leak by bbernard on Wednesday December 07, 2016 @03:33PM (#13125966)

Looks like a lot of fun! :)

I agree that some memory leaks are rather hard to find.

[ Parent | on HN ]