Skip to content

⚡ Bolt: Fix goroutine leak in ScanPorts on premature cancellation - #157

Open
mendsec wants to merge 1 commit into
developfrom
fix-scan-ports-goroutine-leak-6686565228681215997
Open

mendsec wants to merge 1 commit into
developfrom
fix-scan-ports-goroutine-leak-6686565228681215997

Conversation

@mendsec

@mendsec mendsec commented Sep 19, 2026

Copy link
Copy Markdown
Collaborator

What

Fixes a goroutine leak in pkg/ports.ScanPorts during premature context cancellation by wrapping the out <- p send operation in a select block that listens for ctx.Done().

Why

When a consumer stops reading from the unbuffered results channel (e.g., due to cancellation), worker goroutines attempting to send discovered ports block indefinitely on out <- p, leading to severe goroutine and resource leaks over time in high-concurrency scans.

Impact

Ensures zero goroutine leakage when context is canceled mid-scan.

Measurement

Verified by running the test suite, specifically tests checking for goroutine leaks upon cancellation.


PR created automatically by Jules for task 6686565228681215997 started by @mendsec

Fixes a goroutine leak in `pkg/ports.ScanPorts` during premature context cancellation by wrapping the `out <- p` send operation in a `select` block that listens for `ctx.Done()`.

When a consumer stops reading from the unbuffered results channel (e.g., due to cancellation), worker goroutines attempting to send discovered ports block indefinitely on `out <- p`, leading to severe goroutine and resource leaks over time in high-concurrency scans.

This ensures zero goroutine leakage when context is canceled mid-scan.

Co-authored-by: mendsec <12684528+mendsec@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@github-actions
github-actions Bot deleted the fix-scan-ports-goroutine-leak-6686565228681215997 branch September 20, 2026 03:26
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.

1 participant