What operating system are you on ?
What version of gcc/gcj did you use to build PyLucene (if you didn't use the
binaries on the pylucene site) ?
It seems that there is an issue with memory leaks on Linux. Since there don't
seem to be the same issues on Mac OS X or Windows, I suspect there to be an
issue with gcc/gcj or the garbage collector on Linux with PyLucene. Exact
version information would be helpful. Trying to recompile PyLucene with the
very latest gcj snapshot on Linux would also be worth a try. See PyLucene's
INSTALL for instructions.
Andi..
On Sat, 6 Aug 2005, [EMAIL PROTECTED] wrote:
Hi all,
I just coded a twisted + pylucene server. After having live query feeds to
the daemon, I notice the python server's memory just goes up and up.
After it reaches around 1.3GB of memory, I start to get
"GC Warning: Repeated allocation of very large block""
After a minute or two over the 2GB memory mark, I have 4GB memory rhel 4 with
zero swap in use so memory is not the problem, the server dies with
"Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS"
I'm new to python. I tried adding gc.collect() at the end of the searches and
adding "del myvars" at the end as well before the gc.collect(). Still memory
goes up and up with no end in sight. The code base is very small so not sure
where the memory leaks are coming.
Thanks for any help.
Xing Li
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
