Hi Luís, On Wed, Feb 3, 2021 at 5:51 PM Luís Moreira de Sousa via grass-user <grass-user@lists.osgeo.org> wrote: > > Hi Stefan, thank you for the reply. > > The outputs you request are below. v.rast.stats takes about 8 GB of RAM > before failing, only 1/4 of what is available in the workstation. I also > tried increasing the memory parameter but it never goes above 8 GB and fails > all the same.
If I am not mistaken, the memory= parameter isn't used at all in v.rast.stats, hence not passed to v.to.rast: https://github.com/OSGeo/grass/blob/e5afa5a8a0f8e39376f4ddfbda1a62abdef99a21/scripts/v.rast.stats/v.rast.stats.py#L167 For a test, you could use g.gisenv and set the "cache" memory to a higher value (v.to.rast will respect it then): https://grass.osgeo.org/grass78/manuals/variables.html#list-of-selected-internal-grass-environment-variables --> MEMORYMB Eg. # set to 12 GB (default: 300 MB) g.gisenv set="MEMORYMB=12000" Not sure if that would help anyway. However: > Let me know if there is something else I can check. Thank you. yes, you may try with "valgrind": https://grasswiki.osgeo.org/wiki/GRASS_Debugging#Using_Valgrind CMD="v.to.rast input=PSU output=test use=cat memory=10000" valgrind --tool=memcheck --leak-check=yes --show-reachable=yes $CMD --o The output may give some hints (it will be long). Best Markus _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
