Get notifications!

You can opt in to receive email notifications, for example when your questions get answered or when there are new announcements, by following the instructions given here.

Got a problem?

1. Search using the upper-right search box, e.g. using the error message.
2. Try the latest version of tools.
3. Include tool and Java versions.
4. Tell us whether you are following GATK Best Practices.
5. Include relevant details, e.g. platform, DNA- or RNA-Seq, WES (+capture kit) or WGS (PCR-free or PCR+), paired- or single-end, read length, expected average coverage, somatic data, etc.
6. For tool errors, include the error stacktrace as well as the exact command.
7. For format issues, include the result of running ValidateSamFile for BAMs or ValidateVariants for VCFs.
8. For weird results, include an illustrative example, e.g. attach IGV screenshots according to Article#5484.
9. For a seeming variant that is uncalled, include results of following Article#1235.

Jump to another community

PrintReads keeps running out of memory (GC overhead limit exceeded)

I am using base recalibration on human whole genome data and I keep running out of memory. I am running this on a cluster with plenty of memory but it seems that as I increase memory PrintReads is still using up what I provide to it. After trying 1 and 2 cores with 16GB in the java execution (-Xmx) line, in the most recent iteration, I requested 5 cores, each with 20GB of memory and executed the following command:

For what it's worth, the program output seems to show that PrintReads is getting stuck on a relatively innocuous region of chromosome 11 that has 40X coverage. I can "samtools view" the suspect coordinate (+/- 100 bases without issue).

OK, so by bumping up the memory to 80gb, the job finished without error. I did run SAM validation prior to GATK post-processing and it completed without errors. I don't know how the memory requirements break down per # reads or # of readgroups, but at least it worked now. The SAM file has 740M reads in it.