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

[GRASS GIS]

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

Comment (by mmetz):

 Replying to [comment:13 mlennert]:
 >
 > Without (i.e. grass70) my machine became unusable for a while and then
 the module execution stopped after a bit more than 5 minutes because of
 too little memory. With the fix (grass73) it went all the way to 100% of
 writing areas (17 minutes on my machine), but then I got an error
 "Category index is not up to date".

 The -v and -b flags are mutually exclusive. The -v flag is disabled for
 certain input/flag combinations, but this test was missing. Added in trunk
 r68720.
 >
 > However, my colleague's problem was not in the vectorization stage, but
 in the topology building stage. I'm currently testing with -vt and
 VECTOR_LOW_MEM=1. It's been running for about 1 h. I'll see tomorrow what
 the result is...

 The topology building stage might need a lot of memory. If a lot of memory
 is still in use because of a memory leak in the extraction stage, the
 topology building stage is more likely to fail because of an out-of-memory
 error. There is no guarantee that topology building will succeed, but the
 chances for success are higher now that the (hopefully last) memory leak
 in the extraction stage has been fixed. If topology building still fails
 with an out-of-memory error, try again with the environment variable
 GRASS_VECTOR_LOWMEM set.

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