Oho! If a part of the kernel, say a device driver, allocates memory in
"kernel-space" and never explicitly frees it, then there would be a
memory leak inside that device driver. And since the device driver is
somewhat independent of the process that uses the device driver, there
would be no autom
On Tuesday 08 February 2005 17:19, Cristiano Ghirardi wrote:
> it's not clear to me what happens when memory has been allocate with
> g_new or g_realloc and not freed. I mean: obviously this memory
> remains in the user space of the process as an infamous memory leak
> but it seems to me that und
On Tue, 8 Feb 2005 18:19:03 +0100
Cristiano Ghirardi <[EMAIL PROTECTED]> wrote:
> it's not clear to me what happens when memory has been allocate with
> g_new or g_realloc and not freed. I mean: obviously this memory
> remains in the user space of the process as an infamous memory leak
> but it s
Hi,
it's not clear to me what happens when memory has been allocate with
g_new or g_realloc and not freed. I mean: obviously this memory
remains in the user space of the process as an infamous memory leak
but it seems to me that under linux 2.4.26 this memory is not freed
also when the process ha
