Mark DePristo 39bc9e999d Add a test to LocusIteratorByState to ensure that we aren't holding reads anywhere ... -- Run an iterator with 100Ks of reads, each carrying MBs of byte[] data, through LIBS, all starting at the same position. Will crash with an out-of-memory error if we're holding reads anywhere in the system. -- Is there a better way to test this behavior?		2013-01-14 16:30:16 -05:00
..
config	Reorganized the codebase beneath top-level public and private directories,	2011-06-28 06:55:19 -04:00
src	ManagingReferenceOrderedView optimization: don't allow a fresh RefMetaDataTracker in the frequent case where there's no reference meta data	2013-01-14 16:30:16 -05:00
test	Add a test to LocusIteratorByState to ensure that we aren't holding reads anywhere	2013-01-14 16:30:16 -05:00