[postgis-devel] [PostGIS] #1436: shp2pgsql memory leakage

[PostGIS]

#1436: shp2pgsql memory leakage
---------------------------+------------------------------------------------
 Reporter:  strk           |       Owner:  mcayland     
     Type:  defect         |      Status:  new          
 Priority:  medium         |   Milestone:  PostGIS 2.0.0
Component:  loader/dumper  |     Version:  trunk        
 Keywords:                 |  
---------------------------+------------------------------------------------

Comment(by strk):

 It is the UTF8 conversion leaking:
 {{{
 ==21046== HEAP SUMMARY:
 ==21046==     in use at exit: 3,468,357 bytes in 200,647 blocks
 ==21046==   total heap usage: 1,840,844 allocs, 1,640,197 frees,
 6,746,422,052 bytes allocated
 ==21046==
 ==21046== 6 bytes in 1 blocks are definitely lost in loss record 1 of 2
 ==21046==    at 0x4C274A8: malloc (vg_replace_malloc.c:236)
 ==21046==    by 0x4097A1: set_loader_config_defaults (shp2pgsql-
 core.c:763)
 ==21046==    by 0x40BAA5: main (shp2pgsql-cli.c:86)
 ==21046==
 ==21046== 3,468,351 bytes in 200,646 blocks are definitely lost in loss
 record 2 of 2
 ==21046==    at 0x4C274A8: malloc (vg_replace_malloc.c:236)
 ==21046==    by 0x409FCD: utf8 (shp2pgsql-core.c:93)
 ==21046==    by 0x40A45D: ShpLoaderGenerateSQLRowStatement (shp2pgsql-
 core.c:1558)
 ==21046==    by 0x40BF63: main (shp2pgsql-cli.c:346)
 ==21046==
 ==21046== LEAK SUMMARY:
 ==21046==    definitely lost: 3,468,357 bytes in 200,647 blocks
 ==21046==    indirectly lost: 0 bytes in 0 blocks
 ==21046==      possibly lost: 0 bytes in 0 blocks
 ==21046==    still reachable: 0 bytes in 0 blocks
 ==21046==         suppressed: 0 bytes in 0 blocks
 }}}

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1436#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.