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

[GEOS]

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

Comment (by cvvergara):

 @strk
 Can you verify this:

 From what I see:

 The commits of the tag:
 https://github.com/libgeos/geos/releases/tag/3.7.0

 are listed here:
 https://github.com/libgeos/geos/commits/673b993976709d2f72c35c4886327d6f2752fe48

 As you can see there is no commit (from me) involving the shadows on 3.7.0

 I made sure when merging to master that it was done after master was
 changed to 3.8

 On:
 https://git.osgeo.org/gitea/geos/geos/pulls/44

 cvvergara merged 1 commits from cvvergara/geos:fix-shadow into master 2
 weeks ago.

 The history of commits on master shows that the shadow PR was merged after
 the commit labeled:  "Flip master to 3.8 development" that was done one
 month ago.
 https://git.osgeo.org/gitea/geos/geos/commits/branch/master


 So, if something is wrong because of the shadows "fixes", then my
 conclusion is that the milestone for this issue is for 3.8.0-dev not for
 3.7.0

 @Algunenano
 Can you please test if the problem happens on that commit on the following
 commit: 673b993976709d2f72c35c4886327d6f2752fe48
 (on the mean time I will try to understand your process)

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