系统资源不足致设备无法启动，maxFiles/openFiles数值异常偏高求解

Hey there, let's work through this unusual high file handle issue with the iOS Simulator—those numbers (over 11k open files) are way beyond the typical hundreds we see in similar posts, so we'll need to cover both Simulator-specific fixes and deeper system tweaks.

1. First, Audit What's Actually Hogging File Handles #

Before jumping into fixes, let's confirm the source of the problem:

• Open Terminal and run this to get the exact count of open files for the Simulator:

  lsof -p $(pgrep -x Simulator) | wc -l
  

• To see a detailed breakdown of which files are open, run:

  lsof -p $(pgrep -x Simulator)
  

  Look for repeated file patterns—like endless log files, cached assets, or temporary files generated by a misbehaving framework in your app.

2. Simulator-Specific Fixes (Start Here) #

These are the quickest wins to rule out common Simulator bloat:

• Full Simulator Reset: Cached data can pile up over time and cause file handle leaks. Go to the Simulator menu → Device → Erase All Content and Settings. Alternatively, run this Terminal command (note: this wipes all simulator data, back up anything important first):

  xcrun simctl erase all
  

• Update Xcode & Simulator: Older versions of Xcode/Simulator are known to have file handle leak bugs. Make sure you're running the latest stable Xcode and that the Simulator is updated alongside it.
• Cut Back on Concurrent Simulators: Even if the error suggests supporting more devices, running too many simulators at once (10+) can overwhelm the system. Close all simulators, then launch only the one you need—check if the open file count drops significantly.
• Check Your App/Frameworks: If this only happens when running your app, dig into your code:
  • Are you using FileHandle/NSFileHandle without calling close()?
  • Do any third-party SDKs (like logging, analytics, or crash reporting tools) have known file handle leaks? Use Xcode's Instruments → File Activity template to track open/close operations in your app.

3. System-Level Adjustments (For Extreme Cases) #

Since your numbers are way higher than normal, we might need to tweak system limits:

• Adjust Simulator's File Handle Buffer: The error mentions enforcedFilesBuffer—you can modify the Simulator's config to allow more handles:
  1. Open the plist file at ~/Library/Preferences/com.apple.iphonesimulator.plist (use PlistEdit Pro or defaults commands in Terminal).
  2. Add a new key MaxNumberOfFileHandles (type: Number) and set it to a value higher than your current maxFiles (e.g., 20000).
  3. Restart the Simulator.
• Increase System-Wide File Limits:
  • Temporary fix: Run this in Terminal, then launch the Simulator from the same Terminal window (this only lasts until you close the Terminal):

    ulimit -n 20000
    open -a Simulator
    

  • Permanent fix: For macOS Ventura and later, run this command and restart your Mac:

    sudo launchctl limit maxfiles 20000 25000
    

    For older versions, edit /etc/launchd.conf (create it if it doesn't exist) and add:

    limit maxfiles 20000 25000
    

    Then restart your Mac.
• Check for System-Wide Leaks: Other background processes might be eating up file handles. Run lsof | wc -l to see total open files system-wide, then use:

  lsof | sort -nrk 2 | head -20
  

  to find the top processes consuming handles. Close any unnecessary apps/services.

4. Advanced: Debug Simulator-Level Leaks #

If none of the above works, it might be a Simulator bug:

• Enable debug logging for the Simulator:

  defaults write com.apple.iphonesimulator DebugLogging YES
  

  Restart the Simulator, then check the log file at ~/Library/Logs/CoreSimulator/CoreSimulator.log for clues about file handle errors.
• Report the bug to Apple: Use the Feedback Assistant to submit a bug report, including the log file, error screenshot, your Xcode/macOS version, and steps to reproduce the issue.

内容的提问来源于stack exchange，提问作者swiftandRoll