fix(headless): avoid cross-test chrome teardown races

[dwisiswant0]

Proposed changes

Drop global Chrome process sweeping from browser
shutdown.

The previousPIDs snapshot + delta kill logic is
unsafe on shared/parallel runners: a test can
classify another test's Chrome as "new" and kill
it during (*Browser).Close(), triggering
intermittent Rod panics (use of closed network
connection).

Proof

Checklist

• Pull request is created against the dev branch
• All checks passed (lint, unit/integration/regression tests etc.) with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[neo-by-projectdiscovery-dev]

Neo - PR Security Review

No security issues found

Highlights

• Removes global Chrome process sweeping (previousPIDs snapshot + delta kill logic) from Browser.Close() to prevent race conditions in parallel test runners
• Proper cleanup still occurs via launcher.Kill() and engine.Close() methods
• Test helper function maintains deferred cleanup for browser and instance resources

_{Comment @neo help for available commands. · Open in Neo}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dwisiswant0/fix/headless/avoid-cross-test-chrome-teardown-races

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[dwisiswant0]

@coderabbitai create an issue for this, and linked to this PR.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@dwisiswant0: I'll create a GitHub issue for this PR right away.

---

🏁 Script executed:

#!/bin/bash
# Create a GitHub issue for the cross-test chrome teardown races problem

gh issue create \
  --repo projectdiscovery/nuclei \
  --title "fix(headless): avoid cross-test chrome teardown races" \
  --body "## Problem

The \`previousPIDs\` snapshot + delta kill logic in browser shutdown is unsafe on shared/parallel runners. When tests run concurrently, a test can classify another test's Chrome process as \"new\" and kill it during \`(*Browser).Close()\`, triggering intermittent Rod panics due to use of closed network connections.

## Context

This issue is being addressed in PR `#7053` by removing global Chrome process sweeping from browser shutdown.

## References

- Pull Request: https://github.com/projectdiscovery/nuclei/pull/7053
- Requested by: `@dwisiswant0`" \
  --assignee dwisiswant0

Length of output: 54

---

@dwisiswant0: I've successfully created issue #7057 for this PR. The issue describes the cross-test Chrome teardown race condition problem and references PR #7053. It has been assigned to you as requested.

[dwisiswant0]

Dismissing the review. Merging into #7018.