Closed erdikilic closed 1 year ago
This error usually means that your process ran out of memory. It is usually resolved by running on a machine with more memory or running with fewer threads.
Hey @susannasiebert. Thanks for your response.
I will add --memory="16g" --memory-swap="4g" into the docker run commend. Do you have any suggestion for memory adjustment. Local PC can support up to 32GB RAM.
Actually, I am running with 1 thread and sometimes getting sh: 0: Cannot fork sh: 1: Cannot fork
. Then, I am rerunning and it continues.
We run with 16GB default in our pipeline and that's usually ok unless your data has very long frameshifts. Reducing the --downstream-sequence-length
parameter to 200 or 300 can also help with memory.
I don't know what happening but it give me error during the process. It worked for 1 hours and stopped suddenly whit this error.
The commend I used
Log Output