[GRASS-dev] [GRASS GIS] #2045: r.to.vect: use less memory

GRASS GIS trac at osgeo.org
Fri Jul 26 12:20:35 PDT 2013


#2045: r.to.vect: use less memory
------------------------------+---------------------------------------------
 Reporter:  mlennert          |       Owner:  grass-dev@…              
     Type:  enhancement       |      Status:  new                      
 Priority:  normal            |   Milestone:  7.0.0                    
Component:  Raster            |     Version:  svn-trunk                
 Keywords:  r.to.vect memory  |    Platform:  Unspecified              
      Cpu:  Unspecified       |  
------------------------------+---------------------------------------------

Comment(by mmetz):

 Replying to [comment:3 mlennert]:
 > Replying to [comment:2 mlennert]:
 > > Replying to [comment:1 mmetz]:
 > > > Replying to [ticket:2045 mlennert]:
 > > > > Trying to convert a raster file to vector areas on a machine with
 10GB, the process was killed after having used up all memory and swap.
 > > >
 > > > There was a memory leak in r.to.vect, fixed in trunk r57281.
 > >
 > > (and r57281)
 > >
 > > Thanks ! I now get through the "Extracting areas..." part without the
 process being killed. I still see continuous increase in memory usage,
 though, up to 88,5% at the end of the extraction stage. Is this normal ?
 > >
 > > Now it's busy writing areas...
 > >
 >
 > And memory usage continued to increase. The process was killed during
 the "Registering primitives..." step.

 You can try to set the environment variable GRASS_VECTOR_LOWMEM before
 running r.to.vect. GRASS_VECTOR_LOWMEM reduces the amount of memory used
 by vector topology structures (the spatial index is built on disk).

 IOW, r.to.vect might use quite a bit of memory which is difficult to
 change, and the vector topology structures also need memory (in g7 much
 less than in g6).

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2045#comment:4>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list