[geos-devel] [GEOS] #923: Memory leak in GEOSNode

GEOS geos-trac at osgeo.org
Thu Sep 20 09:21:01 PDT 2018

#923: Memory leak in GEOSNode
 Reporter:  Algunenano   |       Owner:  geos-devel@…
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:  3.8.0
Component:  Default      |     Version:  master
 Severity:  Significant  |  Resolution:
 Keywords:               |

Comment (by cvvergara):

 @algun enano

 can you make this tests
 Can you try on 3.7.0 and on master:
 test 1: add at the end of the script `finishGEOS();`
 test 2: only have in the script `initGEOS(test_log, test_error);

 For me without finishGEOS I get
 Memory checking results:
 Potential Memory Leak - 4
 and with finishGEOS
 Memory checking results:
 Potential Memory Leak - 3

 Note that in valgrind the Potential Memory leak mean:
 That  "Memory was allocated and was not subsequently freed before the
 program terminated."

Ticket URL: <https://trac.osgeo.org/geos/ticket/923#comment:14>
GEOS <http://trac.osgeo.org/geos>
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite (JTS).

More information about the geos-devel mailing list