-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Samtools Customview Fails with Unavoidable Segmentation Faults #199
Comments
Hi @ieres-amgen, how technically minded are you? Are you able to test/implement any of these as a feature? |
Hi @chris-cheshire, I am not particularly fluent with nextflow, but I did try splitting the pipe up to ascertain the cause of the break, and found that the |
I found that I was able to resolve by replacing the current process for collecting fragment lengths with the below implementation of Picard CollectInsertSizeMetrics. I note a custom process label for more memory, the setting of avail_mem, and the use of a ${prefix}.tmp file and tail -n+12 on that file to ensure the formatting of this module's ${prefix}.txt file will be correct for the FRAG_LEN_HIST downstream task (otherwise calc_frag_hist.py will encounter a ParserError):
I am not sure if there is an option in Picard to exclude the various header outputs in lines 1-11 of the OUTPUT file, or if a newer version of the software may provide a different format. But this resolved my issues. Thanks! -Ittai |
thank you for your investigation! I will try and roll this in as a feature for the next release. It won't be 3.2 though I am afraid, as this is already about to ship. |
Description of the bug
The "SAMTOOLS_CUSTOMVIEW" process fails on some files due to a segmentation fault, with a core dump, suggesting a memory issue. On my most recent run I allocated 768 GB RAM with 96 CPUs to the task, and it still failed. The input file is fairly large but nothing absurd for a FASTQ, ~15 GB. On slack Harshil suggested that the command may crash due to a lot of piping and offered some ideas to resolve:
Thanks!
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: