Re: [gtk-list] Re: how can I trust glib when it has so manymemleaks?
- From: Ionutz Borcoman <borco borco-ei eng hokudai ac jp>
- To: gtk <gtk-list redhat com>
- Subject: Re: [gtk-list] Re: how can I trust glib when it has so manymemleaks?
- Date: Thu, 18 Mar 1999 16:55:25 +0900
Elliot Lee wrote:
>
> On Thu, 18 Mar 1999, Ionutz Borcoman wrote:
>
> > Havoc Pennington wrote:
> > >
> > > No, Unix-ish systems won't let you do that. All the memory is freed by the
> > > operating system when the program is terminated. However the memory is
> > > never explicitly freed by the program itself, and this is what ccmalloc
> > > checks.
> >
> > Please detail one thing here: memory is alocated by my program using
> > glib. You say UNIX will free all the memory. Why isn't it freeing the
> > memory allocated by glib also ?
>
> It is.
If system frees this memory, how can glib regain it ?
> > What is the use of ccmalloc if memory is freed by system when my
> > program finishes ? Just to ensure that my program doesn't grow too
> > much while running ?
>
> Yes, exactly. And as you've discovered, ccmalloc also isn't very smart
> about even that aspect of memory management.
Please give me a smarter one in this case.
TIA,
Ionutz
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]