[GRASS5] Memory leaks...

Miller, Eric emiller at consrv.ca.gov
Wed Nov 8 13:49:06 EST 2000


Last night I uploaded a revised version of r.random.  Markus noted that it
consumes an inordinate amount of memory (especially noticeable with large
rasters).  I've looked over the code again and again, but can't find the
memory leak.  The module should more or less allocate a fixed amount of
space (there are no looping memory calls).  So, I'm convinced there must be
some memory leakage in one (or more) of the library functions the modules
call.  If anyone has any insight (or wants to poke around) that would be
great.  Library functions called include:

G_get_raster_row(), G_set_null_?_value(), G_is_?_null_value(), and a few
others.

I'm thinking the leakage must be in the G_get_raster_row().  But perhaps
it's something I'm doing in the module (???).  Anyway, memory leaks in
library modules affect all code, so if that's the case we certainly need to
stop them up.

More later...

--  
Eric G. Miller <emiller at consrv.ca.gov> (916) 445-0395
Environmental Specialist II,  Office of Mine Reclamation
"You can't take the low road and claim the high horse." -- anon


---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'



More information about the grass-dev mailing list