hanna f3dacd3c40 Use ByteBuffer.allocateDirect() instead of ByteBuffer.allocate(). ... ByteBuffer.allocateDirect() behaves like Java NIO MappedByteBuffers in that it consumes address space, which counts against our virtual memory allocation; but cannot be destroyed or otherwise freed. This was definitely contributing to the LSF failures that I was seeing, but I'm not yet convinced that it's the sole source of these virtual memory 'leaks'. More tomorrow as the results of my whole exome tests start to roll in. git-svn-id: file:///humgen/gsa-scr1/gsa-engineering/svn_contents/trunk@5693 348d0f76-0448-11de-a6fe-93d51630548a		2011-04-27 02:01:11 +00:00
..
config	Provide a default logger, some config settings, and some doc updates.	2009-04-29 02:06:05 +00:00
src	Use ByteBuffer.allocateDirect() instead of ByteBuffer.allocate().	2011-04-27 02:01:11 +00:00
test	Removing broken imports (boo)	2011-04-26 18:55:25 +00:00