Bug#730460: memory leak in procps-ng

2013-11-26 Thread Jim Warner
Hi Jack, I’m the guy that added the readproc code you found suspect. Please don't think of those buffers as representing a memory leak. Instead, think of them as being statically allocated like this: #define MAX_BUFSZ 1024*64*2 static char src_buffer[MAX_BUFSZ], dst_buffer[MAX_BUF

Bug#730460: memory leak in procps-ng

2013-11-25 Thread Jack Wang
Package: libprocps0 Version: 1:3.3.3-7 We're using libprocps as below: PROCTAB* proc = openproc(PROC_FILLARG | PROC_FILLSTAT); proc_t proc_info; // zero out the allocated proc_info memory memset(&proc_info, 0, sizeof(proc_info)); while (readproc(proc, &proc_info) != NULL) { // <