[GRASS-dev] v.select: increasing memory consumption

[Stefan Blumentrath]

THanks, we`ll try and report back.

-----Original Message-----
From: Markus Neteler <neteler at osgeo.org> 
Sent: fredag 18. januar 2019 07:52
To: Stefan Blumentrath <Stefan.Blumentrath at nina.no>
Cc: GRASS developers list (grass-dev at lists.osgeo.org) <grass-dev at lists.osgeo.org>
Subject: Re: [GRASS-dev] v.select: increasing memory consumption

Hi,

On Thu, Jan 17, 2019 at 2:11 PM Stefan Blumentrath <Stefan.Blumentrath at nina.no> wrote:
>
> Dear all,
>
> A colleague of mine just experienced that v.select in GRASS 7.4.3 (from UbuntuGIS) did not stop allocating memory until the server (Ubuntu 16.04) almost died and he killed the process.
>
> Is that a bug or would v.select have stopped allocating memory at some point before the system gets unusable? Or is this something the user should take care of? If I remember correctly there is a “LOW_MEM option” for v.in.ogr would such a thing be needed here to.
>
> In a multi-user environment this can be a bit tricky…

yeah!

> Any hints? Should I open a ticket (probably hard to reproduce with small test-dataset)?

Please re-run the job with "valgrind", see

https://grasswiki.osgeo.org/wiki/GRASS_Debugging#Using_Valgrind

That will give insights about potential memory leaks. He/you may CTRL-C it on the way to keep the server alive.

Best
Markus