bbuchfink / diamond

Accelerated BLAST compatible local sequence aligner.
GNU General Public License v3.0
1k stars 183 forks source link

Error: Format error: Invalid varint encoding #653

Open alvanuffelen opened 1 year ago

alvanuffelen commented 1 year ago

Using the command with diamond v2.1.0: diamond blastx -q subsample.fq -d nr_cleaned.dmnd -o zymo.daa -F 15 -f 100 --range-culling --top 10 -p 64 -b12 I get the following error

[...]
Processing query block 1, reference block 13/13, shape 2/2.
Building reference seed array...  [0.753s]
Building query seed array...  [0.015s]
Computing hash join...  [0.098s]
Searching alignments...  [0.263s]
Deallocating memory...  [0s]
Deallocating buffers...  [0.641s]
Clearing query masking...  [0s]
Opening temporary output file...  [0s]
Computing alignments... Loading trace points...  [0.008s]
Sorting trace points...  [0.012s]
Computing alignments...  [0.137s]
Deallocating buffers...  [0.002s]
Loading trace points...  [0s]
 [0.161s]
Deallocating reference...  [0.609s]
Loading reference sequences...  [0s]
Deallocating buffers...  [0s]
Joining output blocks... Joining output blocks... Error: Format error: Invalid varint encoding.Error: Format error: Invalid varint encoding.Error: Format error: Invalid varint encoding.
Error: Format error: Invalid varint encoding.
Error: Format error: Invalid varint encoding.
free(): corrupted unsorted chunks
Error: Format error: Invalid varint encoding.Segmentation fault (core dumped)

The error does not happen:

  1. If I use the same command with diamond v2.0.4
  2. If I use another database (e.g. the database from the tutorial) with diamond v2.1.0

The database I used was built with the command: diamond makedb --in cleaned.fa --db nr_cleaned --threads 64 and dbinfo gives:

          Database type  Diamond database
Database format version  3
          Diamond build  154
              Sequences  433397414
                Letters  150975358732
bbuchfink commented 1 year ago

I can reproduce the problem. Will try to provide a fix in the next days.

bbuchfink commented 1 year ago

This should be fixed in version 2.1.1.