Skip to content
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

FASTQC single-end data process doesn't specify number of threads #879

Closed
jfy133 opened this issue Apr 12, 2022 · 2 comments · Fixed by #883
Closed

FASTQC single-end data process doesn't specify number of threads #879

jfy133 opened this issue Apr 12, 2022 · 2 comments · Fixed by #883
Labels
bug Something isn't working next-patch

Comments

@jfy133
Copy link
Member

jfy133 commented Apr 12, 2022

This means we can't increase memory based on the the number of threads, the way fastqc likes it.

Should be added for single-end, as well paired-end to help it cope with large data

@jfy133 jfy133 added the bug Something isn't working label Apr 12, 2022
@jfy133
Copy link
Member Author

jfy133 commented Apr 12, 2022

Repoted by @marcel-keller

@jfy133
Copy link
Member Author

jfy133 commented Apr 12, 2022

Note: if it runs out of memory it hangs on:

Exception in thread "Thread-1" java.lang.OutOfMemoryError: Java heap space
	at uk.ac.babraham.FastQC.Utilities.QualityCount.<init>(QualityCount.java:33)
	at uk.ac.babraham.FastQC.Modules.PerTileQualityScores.processSequence(PerTileQualityScores.java:259)
	at uk.ac.babraham.FastQC.Analysis.AnalysisRunner.run(AnalysisRunner.java:89)
	at java.lang.Thread.run(Thread.java:748)
And never dies

@jfy133 jfy133 mentioned this issue Apr 26, 2022
11 tasks
@jfy133 jfy133 closed this as completed May 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working next-patch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant