Opened 13 years ago

#3594 new defect

Memory leak in filter thing in wfs_get_feature_id.xml

Reported by: rouault Owned by: mapserverbugs
Priority: normal Milestone:
Component: WFS Server Version: unspecified
Severity: normal Keywords:
Cc:

Description

valgrind --leak-check=full mapserv "QUERY_STRING=map=wfs_simple.map&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&TYPENAME=province&featureid=province.Quebec"

shows :

==2482== 4 bytes in 1 blocks are definitely lost in loss record 1 of 15
==2482==    at 0x4C274A8: malloc (vg_replace_malloc.c:236)
==2482==    by 0x4ABCD9: msLayerWhichItems (maplayer.c:403)
==2482==    by 0x48D630: msQueryByRect (mapquery.c:765)
==2482==    by 0x5382B8: FLTApplySimpleSQLFilter (mapogcfilter.c:1188)
==2482==    by 0x53878E: FLTLayerApplyPlainFilterToLayer (mapogcfilter.c:1338)
==2482==    by 0x4ADBDD: msLayerApplyPlainFilterToLayer (maplayer.c:1064)
==2482==    by 0x5386C8: FLTApplyFilterToLayer (mapogcfilter.c:1292)
==2482==    by 0x5177D3: msWFSGetFeature (mapwfs.c:2304)
==2482==    by 0x518ED0: msWFSDispatch (mapwfs.c:2813)
==2482==    by 0x50D253: msOWSDispatch (mapows.c:86)
==2482==    by 0x44E76C: main (mapserv.c:1271)
==2482== 
==2482== 17 (8 direct, 9 indirect) bytes in 1 blocks are definitely lost in loss record 4 of 15
==2482==    at 0x4C267CC: calloc (vg_replace_malloc.c:467)
==2482==    by 0x4ABC85: msLayerWhichItems (maplayer.c:398)
==2482==    by 0x48D630: msQueryByRect (mapquery.c:765)
==2482==    by 0x5382B8: FLTApplySimpleSQLFilter (mapogcfilter.c:1188)
==2482==    by 0x53878E: FLTLayerApplyPlainFilterToLayer (mapogcfilter.c:1338)
==2482==    by 0x4ADBDD: msLayerApplyPlainFilterToLayer (maplayer.c:1064)
==2482==    by 0x5386C8: FLTApplyFilterToLayer (mapogcfilter.c:1292)
==2482==    by 0x5177D3: msWFSGetFeature (mapwfs.c:2304)
==2482==    by 0x518ED0: msWFSDispatch (mapwfs.c:2813)
==2482==    by 0x50D253: msOWSDispatch (mapows.c:86)
==2482==    by 0x44E76C: main (mapserv.c:1271)

Not familiar enough with filter, I couldn't find how to fix that.

Change History (0)

Note: See TracTickets for help on using tickets.