Debugging tool memory errors

Often the tool output contains one of:

MemoryError                 # Python
what():  std::bad_alloc     # C++
Segmentation Fault          # C - but could be other problems too
Killed                      # Linux OOM Killer

Solutions:

• Change input sizes or params
  • Map/reduce?
• Decrease the amount of memory the tool needs
• Increase the amount of memory available to the job
  • Request more memory from cluster scheduler
  • Use job resubmission to automatically rerun with a larger memory allocation
• Cross your fingers and rerun the job

Still have questions?

Want to embed this snippet (FAQ) in your GTN Tutorial?

{% snippet  topics/admin/faqs/galaxy-tool-memory-error.md %}

Persistent URL