AW: [pylucene-dev] MemoryError on Solaris - GC memory leak ?

Thomas Koch koch at orbiteam.de
Wed May 23 05:00:07 PDT 2007


> We had to rebuild GCJ 3.4.6 with LARGE_CONFIG defined to 
> avoid this message.  I checked GCJ 4.2.0, and LARGE_CONFIG 
> still doesn't seem to be defined by default.  The comment 
> from 4.2.0's Makefile.direct still
> reads:
> ...

Aaron,

Thanks for the hint - will try this (we're currently running a build).

> > If there's any other way to get rid of the GC Warning (and memory 
> > leak) that would be of interest of course...
> 
> You could probably divide up your documents, and index, say, 
> 50K in one process, exit, do the next 50K in a new process, 
> etc., tuning the batch sizes as needed.  Inelegant, but it'd 
> probably work.
> 

Well that would be an option - but would of course require some more "batch
overhead" (like saving state and the like). 

Regards
Thomas



More information about the pylucene-dev mailing list