Open frederic-mahe opened 3 months ago
FASTQ and tabulated output is only available with fastq_uniques
when the input is in FASTQ format (not FASTA). VSEARCH therefore terminates with a fatal error message in these cases (written to stderr). I do not think it is necessary to clean up memory in these cases.
With FASTQ input (e.g. "@s1\nA\n+\nI\n@s2\nA\n+\nI\n") all memory is freed as expected.
When using
vsearch
with either fastq-output (--fastqout
) or tabulated-output (--tabbedout
),valgrind
reports that there are 47,088 bytes in 17 blocks still in use at exit. Other dereplication command are not affected.Code to reproduce the issue: