Re: [gnome-db] Memory leaks



On 6/4/07, Piotr Pokora <piotrek pokora gmail com> wrote:

Hi!

==13349== 16 bytes in 4 blocks are definitely lost in loss record 692 of
2,137
==13349==    at 0x40234B0: malloc (vg_replace_malloc.c:149)
==13349==    by 0x50F8DB5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.12)
==13349==    by 0x510C238: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.12)
==13349==    by 0x4FFBA01: gda_column_set_title (gda-column.c:397)
==13349==    by 0x52AC031: gda_mysql_recordset_new
(gda-mysql-recordset.c:916)
==13349==    by 0x52A61A1: process_sql_commands (gda-mysql-provider.c:485)
==13349==    by 0x507AC10: gda_server_provider_execute_command
(gda-server-provider.c:642)
==13349==    by 0x50034A5: gda_connection_execute_command
(gda-connection.c:1144)
==13349==    by 0x50037CF: gda_connection_execute_select_command
(gda-connection.c:1231)
==13349==    by 0x4F878F7: ???
==13349==    by 0x4F9E4A9: ???
==13349==    by 0x4F9EC1B: ???

==13349== 16 bytes in 4 blocks are definitely lost in loss record 690 of
2,137
==13349==    at 0x40234B0: malloc (vg_replace_malloc.c:149)
==13349==    by 0x50F8DB5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.12)
==13349==    by 0x510C238: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.12)
==13349==    by 0x4FFBB1B: gda_column_set_name (gda-column.c:360)
==13349==    by 0x52AC044: gda_mysql_recordset_new
(gda-mysql-recordset.c:918)
==13349==    by 0x52A61A1: process_sql_commands (gda-mysql-provider.c:485)
==13349==    by 0x507AC10: gda_server_provider_execute_command
(gda-server-provider.c:642)
==13349==    by 0x50034A5: gda_connection_execute_command
(gda-connection.c:1144)
==13349==    by 0x50037CF: gda_connection_execute_select_command
(gda-connection.c:1231)
==13349==    by 0x4F878F7: ???
==13349==    by 0x4F9E4A9: ???
==13349==    by 0x4F9ECBC: ???

gda_column_finalize doesn't free name or title

I was able to "fix" this locally by adding g_free for particular members.
Unfortunatelly I had no time to investigate further reports:

==13349== 20 bytes in 2 blocks are definitely lost in loss record 820 of
2,137
==13349==    at 0x40234B0: malloc (vg_replace_malloc.c:149)
==13349==    by 0x50F8DB5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.12)
==13349==    by 0x510C238: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.12)
==13349==    by 0x52AC124: gda_mysql_recordset_new
(gda-mysql-recordset.c:909)
==13349==    by 0x52A61A1: process_sql_commands (gda-mysql-provider.c:485)
==13349==    by 0x507AC10: gda_server_provider_execute_command
(gda-server-provider.c:642)
==13349==    by 0x50034A5: gda_connection_execute_command
(gda-connection.c:1144)
==13349==    by 0x50037CF: gda_connection_execute_select_command
(gda-connection.c:1231)
==13349==    by 0x4F878F7: ???
==13349==    by 0x4F9E4A9: ???
==13349==    by 0x4F9ECBC: ???
==13349==    by 0x4F9EDF3: ???
==13349==
==13349==
==13349== 21 bytes in 21 blocks are definitely lost in loss record 844 of
2,137
==13349==    at 0x40234B0: malloc (vg_replace_malloc.c:149)
==13349==    by 0x50F8DB5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.12)
==13349==    by 0x510C238: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.12)
==13349==    by 0x5080D4D: gda_binary_to_string (gda-value.c:2184)
==13349==    by 0x5083BF5: binary_to_string (gda-value.c:248)
==13349==    by 0x5184424: g_value_transform (in
/usr/lib/libgobject-2.0.so.0.1200.12)
==13349==    by 0x5168590: g_object_set_property (in
/usr/lib/libgobject-2.0.so.0.1200.12)
==13349==    by 0x4FBB822: ???
==13349==    by 0x4FBB944: ???
==13349==    by 0x4FBBDDC: ???
==13349==    by 0x4FB0893: ???
==13349==    by 0x4FCCEEF: ???

This is from gda 3.0.1.

Thanks, I'll look at that ASAP.

Vivien



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]