[GRASS-dev] v.in.ogr eats all memory
Hamish
hamish_nospam at yahoo.com
Fri May 19 01:20:15 EDT 2006
> 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).
Usually you can get away with remote login if it is X that locked up,
with a frozen kernel you have less options.. ctrl-alt-F1 sometimes?
> 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.
attempt G_malloc(),G_free() of estimated size before processing. Back in
the mailing list archives somewhere I figured out the current bytes per
vector point needed (with valgrind) and suggested this?
I don't know how to query available memory in a cross platform way.
> I just wonder why the kernel doesn't take care.
?
Hamish
More information about the grass-dev
mailing list