Originally posted by Eteleeb
Aurelien
-
I moved on other projects since then, and I can't remember how I fixed (or dealt with) this error anymore. I know I got the pipeline running on the same machines, so the solution wasn't to add memory.
Aurelien -
AFAIK, this always indicates that an attempt at allocating memory failed.Originally posted by Aurelien Mazurie View Post
This can be a result of running out of memory (due to actual need or a memory leak), an attempt to allocate a stupidly large amount of memory via a broken calculation, or heap fragmentation (so there's enough in total, just not enough in one chunk). You also could be hitting ulimits - check if there are any.
Try monitoring the consumed resources as it runs (e.g. using top), or if that isn't enlightening, maybe see if you can enable detailed logging. Last resort would be a debugger or some other tool to track memory allocations, and see what you see.Leave a comment:
-
Dreaded (because unresolved) bad_alloc error
Greetings,
I run into a 'std::bad_alloc()' error when processing a 500MB BAM file with cufflinks on a 8BG machine. The exact error message is
I saw many posts about this 'bad_alloc' error, which seams to be related to memory problems. For example,Code:. . . > Processed 17748 loci. [*************************] 100% > Map Properties: > Total Map Mass: 14607725.69 > Read Type: 54bp single-end > Fragment Length Distribution: Gaussian (default) > Estimated Mean: 205.82 > Estimated Std Dev: 73.30 [16:12:46] Assembling transcripts and estimating abundances. > Processing Locus EG_1:2534992-2535117 [************************ ] 99%terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc
However none of those posts received an answer. Does anybody have an idea why this error occurs and how to fix it? I tried to run the same process on a Mac with 4 cores and 8GB of RAM, and a Linux 64bits with 4 cores and 12GB of RAM, with the same result.
Best,
Aurelien
-
CRISPR/Cas9 sparked the gene editing revolution for both research and therapeutics.1 But this system still showed severe issues that limited its applications. The most prominent were the heavy reliance on PAM sequences, delivery limitations, double-stranded breaks that prompt unintended edits and cell death, and editing inefficiency (both in targeting and in knock-in reliability).
Despite this, “CRISPR helped turn genome editing from a specialized technique into...07-31-2026, 11:01 AM -
Proteomics platforms are evolving rapidly, with advances in mass spectrometry and affinity-based approaches expanding what researchers can detect and at what scale. As the field moves toward deeper proteome coverage and clinical applications, scientists face an increasingly complex landscape of tools. This article will explore how researchers are navigating these choices to find the right platform for their work.
The systematic characterization of the human proteome has...07-20-2026, 11:48 AM
Leave a comment: