memory footprint about xatlas HOT 2 CLOSED

Hi,

For 30x WES, xAtlas should use around 3-4G of resident memory.

Which version of htslib are you using? And is this reproducible if you omit the -t option? I suspect that this might be a memory leak found in some older versions of htslib related to the BGZF decompression thread pool, since I might have seen similar behavior before with xAtlas built with older htslib versions. xAtlas uses htslib's BGZF decompression thread pool to enable multithreaded BAM decompression when using the -t option.

from xatlas.

Hi,
Leave out the -t option works like a charm!

BTW, I'm using the latest htslib 1.8 in compiling xAtlas. I'll try some older versions to see if the problem persists.

from xatlas.