Closed iAvicenna closed 7 months ago
Hi,
I am busy these days, but I will fix this bug as soon as possible.
Cheers,
Hi,
I apologize for the terrible delay in answering this issue. I am sorry, but, using the latest version (dev), I couldn't reproduce the memory problem. I try the same compiler and OS.
What is the specific CPU ISA you are using (x86, ARM, ...)? Let us try to reproduce this problem and fix it.
May be related to issue #87? Have a look a the latest commit to development
, (commit https://github.com/smarco/WFA2-lib/commit/1d970397af1496a6dba722cfa705b18e2fcf4bd0).
Hello,
I have been using wfa2 as a part of a script that analyses ngs data. I noticed that when I tweaked the parameters in a certain (but not unreasonable way) it crashes once in a while. I isolated it to three sequences, which when analysed one after the other causes the program to crash. I stripped down the whole thing into a bare minimum program which still crashes and is given below:
I ran this with valgrind and the part of the log that pertains to the error is (there is a bunch of stuff that appears because wf_aligner was not freed due to a crash):
I also ran this with gdb to see exactly where it crashes and it gives the fault here
printing the offset value produces this:
Note that I have tested valgrind with other input (for instance only the first two sequences above) and it produces a clean log with such examples (note that for valgrind I had to compile wfa2 with MARCH_FLAG="" BUILD_WFA_PARALLEL="0", otherwise it produces some warnings specific to these).
Further info:
Let me know if there is any other diagnostics I can produce, this is as far as I could go with gbp and valgrind since I don't know the internal details of wfa2. I wonder if there is a function to reset the internal state of a wavefront_aligner_t object to its default state without deleting which would perhaps temporarily remedy the problem until a patch?
Thanks