[GRASS-dev] Re: [GRASS GIS] #837: Memory leaks in r.example

GRASS GIS trac at osgeo.org
Tue Dec 15 22:18:12 EST 2009


#837: Memory leaks in r.example
----------------------+-----------------------------------------------------
  Reporter:  sprice   |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect   |      Status:  closed                   
  Priority:  normal   |   Milestone:  6.4.0                    
 Component:  default  |     Version:  svn-releasebranch64      
Resolution:  wontfix  |    Keywords:                           
  Platform:  MacOSX   |         Cpu:  OSX/Intel                
----------------------+-----------------------------------------------------
Changes (by glynn):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 Replying to [ticket:837 sprice]:

 > In r.example, there are many small memory leaks in basic functions.

 We don't care about "fixed" memory consumption, i.e. the use of a certain
 amount of memory for the process overall, or for each library, or for each
 map. It's only considered a "leak" if the memory usage will grow during
 normal processing, i.e. consuming memory (unnecessarily) per raster row,
 or per vector element.

 If you try to use the GRASS libraries from a persistent application (one
 which performs an unlimited number of operations until it is explicitly
 terminated), you lose. The libraries weren't designed for that purpose,
 aren't suitable for that purpose, and will probably never be suitable for
 that purpose. And memory usage is the least of the issues.

 Closing as "wontfix". If you have details of any actual '''leaks''', feel
 free to reopen.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/837#comment:2>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list