build_timezone leaks timezonefile reference

Bug #1111628 reported by Colin Watson on 2013-01-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Fix Released
indicator-datetime (Ubuntu)

Bug Description

==14362== 30 (16 direct, 14 indirect) bytes in 1 blocks are definitely lost in loss record 1,984 of 3,994
==14362== at 0x482FB34: malloc (vg_replace_malloc.c:270)
==14362== by 0x4F4C2ED: standard_malloc (gmem.c:85)
==14362== by 0x4F4C36B: g_malloc (gmem.c:159)
==14362== by 0x4F5F6AF: g_slice_alloc (gslice.c:1003)
==14362== by 0x4F5F6ED: g_slice_alloc0 (gslice.c:1029)
==14362== by 0x4EE3071: g_type_create_instance (gtype.c:1892)
==14362== by 0x4ECF989: g_object_constructor (gobject.c:1855)
==14362== by 0x4ECF307: g_object_newv (gobject.c:1638)
==14362== by 0x4ECF177: g_object_new (gobject.c:1548)
==14362== by 0x4D5A8B1: _g_local_file_new (glocalfile.c:292)
==14362== by 0x4D63FEB: g_local_vfs_get_file_for_path (glocalvfs.c:84)
==14362== by 0x4CFF707: g_vfs_get_file_for_path (gvfs.c:97)
==14362== by 0x4CC0889: g_file_new_for_path (gfile.c:5910)
==14362== by 0xE69B: build_timezone (datetime-service.c:1088)
==14362== by 0xF2A3: main (datetime-service.c:1470)

timezonefile can safely be unreferenced here to quieten valgrind.

Related branches

Changed in indicator-datetime:
status: New → Triaged
importance: Undecided → Medium
Changed in indicator-datetime:
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-datetime - 12.10.3daily13.02.06-0ubuntu1

indicator-datetime (12.10.3daily13.02.06-0ubuntu1) raring; urgency=low

  [ Colin Watson ]
  * build_timezone leaks timezonefile reference (LP: #1111628)

  [ Automatic PS uploader ]
  * Automatic snapshot from revision 206
 -- Automatic PS uploader <email address hidden> Wed, 06 Feb 2013 02:01:12 +0000

Changed in indicator-datetime (Ubuntu):
status: New → Fix Released
Charles Kerr (charlesk) on 2013-11-06
Changed in indicator-datetime:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers