Skip to content

Suggest --huge flag when BrokenProcessPool crash occurs#431

Merged
wdecoster merged 4 commits intomasterfrom
copilot/fix-issue-430
Mar 17, 2026
Merged

Suggest --huge flag when BrokenProcessPool crash occurs#431
wdecoster merged 4 commits intomasterfrom
copilot/fix-issue-430

Conversation

Copy link
Contributor

Copilot AI commented Mar 17, 2026

When processing very large files (e.g. 82GB BAMs) without --huge, nanoget's ProcessPoolExecutor can OOM-kill a worker, raising BrokenProcessPool with no actionable guidance for the user.

Changes

  • nanoplot/NanoPlot.py: Import concurrent.futures and add a specific except concurrent.futures.BrokenExecutor handler (base class of BrokenProcessPool) before the generic except Exception fallback. On match, logs the crash and prints:
A worker process crashed, likely due to insufficient memory.
If you are working with a very large file, please try running NanoPlot with the --huge flag.

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

…sing

Co-authored-by: wdecoster <11660522+wdecoster@users.noreply.github.com>
Copilot AI changed the title [WIP] [NANOPLOT-430] Fix issue related to huge datasets Suggest --huge flag when BrokenProcessPool crash occurs Mar 17, 2026
Copilot AI requested a review from wdecoster March 17, 2026 10:08
@wdecoster wdecoster marked this pull request as ready for review March 17, 2026 10:23
@wdecoster wdecoster merged commit ebdf07a into master Mar 17, 2026
2 checks passed
@wdecoster wdecoster deleted the copilot/fix-issue-430 branch March 17, 2026 10:29
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

Successfully merging this pull request may close these issues.

2 participants