Closed grinning-bat closed 3 months ago
Sorry for my late response. This is indeed very strange - and would be hard to debug without being able to reproduce the issue. Did you compile from source or run the bioconda version? Did you have any additional information in your terminal output (e.g. backtrace)? Does this reproduces if you run it again?
Another thing to rule out - is it possible you are running out of memory?
Hello. I believe this one was installed from bioconda (see the first block in OP). Bug is reproducible, assembly takes many days, so I tried it only twice. Now I'm running flye-modules with parameters from "ERROR: Command" line under gdb to get a stack trace. Would also appreciate some hints on debug techniques. The only option to run flye on my dataset is HPC cluster (we don't have dedicated 512G RAM node) and I'm using gdb target remote and gdbserver for debugging. Unfortunately it's rather buggy on itself.
RAM usage recorded in the log is about 220Gb and there is a scheduler-imposed limit which is less than the real installed size (500G of 512G installed), so I'd rather expect to see the task being killed by a SLURM than dying due to mem allocation failure.
UPD: this time process running under gdb finished correctly. Hard to say why, failed two times before. So "can't repro" I guess...
Hi! Thanks for your wonderful work! I've got a crash while assembling ONT reads.
The only thing I know about the error: "corrupted double-linked list" in the log when "Extending reads" was at 100%. Tried to find this message in the source code, but no luck. If you need additional debug info/data files - please don't hesitate to tell how to collect/send.
Running on conda, version: