[GRASS-dev] v.in.ogr eats all memory
Stephan Holl
holl at gdf-hannover.de
Fri May 19 03:21:33 EDT 2006
Hello Markus,
On Thu, 18 May 2006 18:29:18 +0200 Markus Neteler <neteler at itc.it>
wrote:
> Hi,
>
> importing a big SHAPE file, it appeared that most
> of the operating was shifted to swap space (Linux). I
> had to reboot the machine (no remote login, not even
> caplock worked).
Second that.
Had that with a large OCI-dataset all the time and was wondering why
this works on one maschine (1GB RAM) and not on anotherone (256MB
RAM)...
> Question: Can we add some test to avoid that more
> than xx percent of the memory are used? There won't
> be any hot plugin of extra RAM, so v.in.ogr should
> exit with memory allocation error. I just wonder why
> the kernel doesn't take care.
I would also like to see such a feature. I have run that through
valgrind, perhaps someone more knowledgeable could have a look at it?
I have provided it here:
http://www.gdf-hannover.de/~holl/tmp/valgrind_v.in.ogr.log.pid26607
Best regards
Stephan
--
GDF Hannover - Solutions for spatial data analysis and remote sensing
Hannover Office - Mengendamm 16d - D-30177 Hannover
Internet: www.gdf-hannover.de - Email: holl at gdf-hannover.de
Phone : ++49-(0)511.39088507 - Fax: ++49-(0)511.39088508
More information about the grass-dev
mailing list