GNOME Bugzilla – Bug 313868
leak in the neon method
Last modified: 2006-01-09 20:59:31 UTC
Valgrind reports: ==2729== 28848 (48 direct, 28800 indirect) bytes in 3 blocks are definitely lost in loss record 5486 of 8566 ==2729== at 0x1B903882: malloc (vg_replace_malloc.c:149) ==2729== by 0x1DAF1A5C: ne_calloc (ne_alloc.c:64) ==2729== by 0x1DAEDB2B: ne_add_response_header_handler (ne_request.c:629) ==2729== by 0x1DAE9A43: add_default_header_handlers (http-neon-method.c:1144) ==2729== by 0x1DAEAF55: http_transfer_start (http-neon-method.c:2250) ==2729== by 0x1DAEB242: do_open (http-neon-method.c:2389) ==2729== by 0x1C1667FA: gnome_vfs_open_uri_cancellable (gnome-vfs-cancellable-ops.c:57) ==2729== by 0x1C17071E: _gnome_vfs_job_execute (gnome-vfs-job.c:964) ==2729== by 0x1C16F863: thread_routine (gnome-vfs-job-slave.c:64) ==2729== by 0x1C17EFCC: thread_entry (gnome-vfs-thread-pool.c:186) ==2729== by 0x1C79CAC3: g_thread_create_proxy (gthread.c:564) ==2729== by 0x1C750B88: start_thread (in /lib/libpthread-2.3.90.so) ==2729== by 0x1C8A817D: clone (in /lib/libc-2.3.90.so)
Another one: ==2729== 28848 (540 direct, 28308 indirect) bytes in 3 blocks are definitely lost in loss record 6201 of 8566 ==2729== at 0x1B903882: malloc (vg_replace_malloc.c:149) ==2729== by 0x1DAF1A5C: ne_calloc (ne_alloc.c:64) ==2729== by 0x1DAF3A1C: ah_create (ne_auth.c:1007) ==2729== by 0x1DAEDD36: ne_request_create (ne_request.c:554) ==2729== by 0x1DAEAF2F: http_transfer_start (http-neon-method.c:2236) ==2729== by 0x1DAEB242: do_open (http-neon-method.c:2389) ==2729== by 0x1C1667FA: gnome_vfs_open_uri_cancellable (gnome-vfs-cancellable-ops.c:57) ==2729== by 0x1C17071E: _gnome_vfs_job_execute (gnome-vfs-job.c:964) ==2729== by 0x1C16F863: thread_routine (gnome-vfs-job-slave.c:64) ==2729== by 0x1C17EFCC: thread_entry (gnome-vfs-thread-pool.c:186) ==2729== by 0x1C79CAC3: g_thread_create_proxy (gthread.c:564) ==2729== by 0x1C750B88: start_thread (in /lib/libpthread-2.3.90.so) ==2729== by 0x1C8A817D: clone (in /lib/libc-2.3.90.so)
Marking as duplicate of bug 169826 *** This bug has been marked as a duplicate of 169826 ***