Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
ORG.Asm
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19,166
    • Issues 19,166
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ORG.Asm
  • ORG.Asm
  • Issues
  • #36

Closed
Open
Opened Apr 28, 2016 by Rob Ness@rwness

oa unfold memory leak?

I have a potentially strange memory leak in oa unfold. I am assembling 21 chloroplast genomes and of those, 16 run quite quickly and finish. 3 have been running in buildgraph for over 24hrs (compared to a few hours for the others) and 2 fail during unfold. The 2 that fail in unfold are both running out of memory - which is shocking because there is 512Gb of available memory. When I watch the process its climbing up into >90% of available memory used and running for hours before it is killed by the system. The only difference I can see between these 5 samples and the 16 that run well is that they have ~10X less estimated chloroplast coverage than others. If you like I could share the graphs etc.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: org-asm/org-asm#36