Mark DePristo 641c6a361e Fix nasty memory leak in new data thread x cpu thread parallelism ... -- Basically you cannot safely use instance specific ThreadLocal variables, as these cannot be safely cleaned up. The old implementation kept pointers to old writers, with huge tribble block indexes, and eventually we crashed out of integration tests -- See http://weblogs.java.net/blog/jjviana/archive/2010/06/10/threadlocal-thread-pool-bad-idea-or-dealing-apparent-glassfish-memor for more information -- New implementation uses a borrow/return schedule with a list of N TraversalEngines managed by the MicroScheduler directly.		2012-09-10 20:14:14 -04:00
..
config	Reorganized the codebase beneath top-level public and private directories,	2011-06-28 06:55:19 -04:00
src	Fix nasty memory leak in new data thread x cpu thread parallelism	2012-09-10 20:14:14 -04:00
test	Refactor TraversalEngine to extract the progress meter functions	2012-09-10 20:14:13 -04:00