Closed jbedo closed 3 years ago
Thanks. I've already encountered this one myself and have started working on a fix.
Thanks for your efforts! Let me know if you need me to test a patch.
Please can you try cf636091cf9b022a6ed13bc0add4e76b9176f4bd?
Testing now, I'm unfortunatly stuck in our computing queue waiting for an allocation. Hopefully won't be too long.
The specific issue appears to be resolved, though I now seem to have a hanging issue where it gets stuck waiting for a futex. If I can get more details I'll open a separate issue for that.
Ok - I'm no longer seeing this issue in my runs either so I'll close. Please do open another issue for the hanging problem.
I'm hitting the hanging waiting for a futex also. Will see if I can find a way to replicate it and open a new issue.
Describe the bug
Calling commences but after some progress octopus terminates with an
free()
error (see log). Seems to be pretty common, happens on ~10% of our cohort. The entire cohort called fine with 0.7.0.Version 0.7.1
Command Command line to install octopus:
Command line to run octopus:
Additional context Add any other context about the problem here, e.g.
Reference [e.g. hg19]. Please provide link to fasta if atypical. grch38
BAM files (if possible). Unfortunately not, it's patient data.