Skip to content
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

[Bug Report] hisat2-align exited with value 137, space complexity of hisat2 #423

Open
bayegy opened this issue Dec 11, 2023 · 0 comments
Open

Comments

@bayegy
Copy link

bayegy commented Dec 11, 2023

Issue Description

I encountered an error while running the hisat2 program. During the alignment stage, hisat2-align exited with value 137. I would like to seek assistance in understanding the factors that may affect hisat2's memory usage, as well as inquire about its space complexity.

Environment Information

  • Operating System: [ubuntu20.04]
  • hisat2 version: [2.2.1]
  • RAM Capacity: 1T
  • Number of Threads: 2
  • Sequencing Data Size: 6G
  • Reference Genome: Bombyx mori species (RefSeq), less than 1G
  • Sequence Preprocessing Tool: fastp

Steps to Reproduce

  1. Perform sequence filtering using fastp.
  2. Run hisat2-align with the given settings mentioned above.
  3. Observe excessive memory usage and program termination with value 137.

Expected Behavior

I expected hisat2 to complete the alignment successfully without encountering excessive memory usage or program termination.

Additional Context

I noticed that for some samples, which were processed using less than 300G of memory, hisat2 executed successfully. However, for other samples, hisat2 required more than 1T of memory, leading to the error mentioned above.

I would appreciate any insights on the factors that influence hisat2's memory usage and the space complexity associated with using hisat2.

Please let me know if there is any further information needed to diagnose and address this issue.

Thank you for your attention and support.

Best regards,
bayegy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant