[GRASS-dev] DBF driver (severe?) memory leak

Markus Neteler neteler at osgeo.org
Thu Apr 2 07:20:36 EDT 2009


hi,

I have tried to run r.random with vector output on a large (400mega
cells) raster
map. After 3% of writing out the vector stuff I had to cancel due to severe
swapping (and 4GB RAM). "top" shows that all memory is eaten by the
DBF driver.

Trying the same with the SQLite driver worked well, no memory consumption
at all.

I tried this to trace the memory leak:
CMD="r.random pat_dtm5m vector_output=vectrandom30percent n=30% --o"
valgrind --tool=memcheck --leak-check=yes --show-reachable=yes  $CMD --o

but it doesn't reach the DBF driver (leaks also in the vector part but not
relevant here).

How to do that properly?

Markus


More information about the grass-dev mailing list