[pylucene-dev] java core dump -- can't allocate larger thread
janssen at parc.com
Fri Mar 28 19:48:32 PDT 2008
> >> Ouch. Maybe you can workaround the problem by reusing threads from a pool
> >> instead of allocating 73 of them ?
> > More like 80. But each thread should "die" and be GC'd, so the VM is
> > supposed to be maintaining that thread pool. I wonder if in fact they
> > are not being GC'd.
> Quite possibly so. Are you calling env.detachCurrentThread() from the
> threads as they terminate ? (this has been crashy, be sure to release all
> objects that point to java objects from that thread first).
Hmmm. OS X "Thread Viewer" shows that the temporary thread is indeed
going away (though whether the Java data structures associated with
the thread go away is another matter). I'll add detachCurrentThread()
and hope for the best.
More information about the pylucene-dev