Re: GConf
- From: James Henstridge <james daa com au>
- To: Anil Kumar Putla <anil gdit iiit net>
- Cc: Havoc Pennington <hp redhat com>, gnome-devel-list gnome org
- Subject: Re: GConf
- Date: Mon, 21 Oct 2002 09:14:15 +0800
Anil Kumar Putla wrote:
Hi,
I just missed that line. g_free(str);
I am just worried about the output of g_mem_profile(), when i am using
gconf. Just checkout the output of g_mem_profile().
GLib Memory statistics (failing operations):
--- none ---
Total bytes: allocated=199865, zero-initialized=11936 (5.97%),
freed=179441 (89.78%), remaining=20424
MemChunk bytes: allocated=11864, freed=0 (0.00%), remaining=11864
In such a short program, you are likely seeing the effects of one time
initialisations of various internal structures. These structures
generally aren't freed (which is not generally a problem). If you
changed your example to lookup 100 times as many strings, and it leaked
100 times as much memory then it would be a bug.
James.
--
Email: james daa com au | Linux.conf.au http://linux.conf.au/
WWW: http://www.daa.com.au/~james/ | Jan 22-25 Perth, Western Australia.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]