-
Notifications
You must be signed in to change notification settings - Fork 134
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
megahit v1.2.9 Exit code 11 #310
Comments
Good evening, I'd really appreciate your help. I am also getting this same error running on a machine with 1Tb RAM (specified 900GB in the command). I don't think that its a memory issue. Here's my log with catchsegv executed. (base) [jmwhitha@bridges2-login012 jmwhitha]$ cat slurm-3475261.out RAX: ffffffffffffffff RBX: 00007ffc1abc1e40 RCX: 0000000000000010 RIP: 0000558cbf9e5185 EFLAGS: 00010a07 CS: 0033 FS: 0000 GS: 0000 Trap: 0000000d Error: 00000000 OldMask: 00000000 CR2: 00000000 FPUCW: 0000037f FPUSW: 00000000 TAG: 00000000 ST(0) 0000 0000000000000000 ST(1) 0000 0000000000000000 Backtrace: Memory map: 149e08000000-149e08021000 rw-p 00000000 00:00 0 |
I'm seeing this error sporadically happen, even with the test command: FROM alpine:latest
RUN apk update && apk add --no-cache python3 && \
wget https://github.com/voutcn/megahit/releases/download/v1.2.9/MEGAHIT-1.2.9-Linux-x86_64-static.tar.gz && \
mkdir /megahit && tar zvxf MEGAHIT-1.2.9-Linux-x86_64-static.tar.gz --strip-components=1 -C /megahit && \
rm MEGAHIT-1.2.9-Linux-x86_64-static.tar.gz
ENV PATH="/megahit/bin:${PATH}"
WORKDIR /data
ENTRYPOINT ["megahit"]
For me, this typically works 3/4 times or so... but randomly fails... |
Good afternoon,
I left megahit running yesterday evening and came in today and came across the
Error code -11
. Before successfully running megahit I had problems with fq.gz files but but after uncompressing them it ran fine until the error. I am running megahit through the conda environment. here is a copy of the log. I am running with dual intel xeon (10core 20 threads each) and 128gb RAMlog.txt
The text was updated successfully, but these errors were encountered: