Excessive Spawning of lsof

[slm-sean]

Checklist

• I searched existing issues and this hasn't been reported

Area

Backend

Operating System

macOS

Version

2.7.2

What happened?

When running the main branch of auto-claude, run with npm start and npm start dev, the auto-claude application appears to spawn 10+ separate processes of lsof when running tasks, consuming all available CPU resources.

Steps to reproduce

npm start

Start a task in auto-claude from the Kanban board.

Monitor system utilization and lsof processes in Activity Monitor.

Expected behavior

Reduce cpu utilization and excessive lsof spawning.

Logs / Screenshots

<img width="1127" height="1092" alt="Image" src="https://github.com/user-attachments/assets/69f22df8-aff9-4871-93e7-882fe70b751e" />

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Task Appears Stuck: Task Runner Crash Loop (File Not Found) #147
• Cannot view modified files or open task in terminal or how to review before merge? #117

👤 Suggested Assignees

• Jorisslagter
• virtuman

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[github-actions]

👋 Thanks for opening your first issue!

A maintainer will triage this soon. In the meantime:

• Make sure you've provided all the requested info
• Join our Discord for faster help

[joelfuller2016]

@openhands-agent Please investigate and fix this excessive process spawning issue.

Issue Summary: Excessive spawning of lsof process on macOS - causing performance degradation and resource exhaustion.

Type: Backend bug (macOS-specific)

Platform: macOS

Investigation Areas:

1. apps/backend/ - Process management, file descriptor checks
2. Search for lsof usage in the codebase
3. Check for loops or repeated calls that spawn lsof
4. Review any file/port monitoring logic

Required Fix:

1. Find all locations where lsof is being called
2. Identify the cause of excessive spawning (loop, timer, event handler)
3. Implement proper throttling or caching for lsof results
4. Consider alternative approaches that don't require frequent lsof calls
5. Add rate limiting to prevent resource exhaustion

Target Branch: develop