Apple developers,
I have identified a memory leak issue in the `configd` process on macOS that I would like to report. This system process runs continuously in the background to manage network and system configuration, but I have noticed its memory usage increase steadily over time without release.
Details:
1. I reported this issue to Apple Support a month ago but have not received a response or acknowledgement yet. I am reporting it again here in the hopes of escalating awareness and priority.
2. This memory leak in a core system process is a serious issue, as it will degrade system performance and stability over time if left unaddressed. `configd` is running 24 hours a day, so even a small leak accumulates quickly.
3. I have provided all necessary data with my original report to help diagnose and fix this issue, including:
- https://discussions.apple.com/thread/254771724
- https://feedbackassistant.apple.com/feedback/12089791
- Figures
4. I have isolated this to the `configd` process by monitoring memory usage of all system processes over time. `configd` is the only one showing steady growth. A reboot temporarily fixes it, but the leak quickly returns.
Please look into fixing this memory leak issue in `configd` as soon as possible. While new features are exciting, ensuring the stability and performance of core system functions like `configd` should be a top priority. Let me know if you need any additional information from me to properly diagnose and patch this leak.
Thank you
To other Mac users:
You can check this issue by running: sudo vmmap -swapped `pgrep configd`
Best
I have identified a memory leak issue in the `configd` process on macOS that I would like to report. This system process runs continuously in the background to manage network and system configuration, but I have noticed its memory usage increase steadily over time without release.
Details:
1. I reported this issue to Apple Support a month ago but have not received a response or acknowledgement yet. I am reporting it again here in the hopes of escalating awareness and priority.
2. This memory leak in a core system process is a serious issue, as it will degrade system performance and stability over time if left unaddressed. `configd` is running 24 hours a day, so even a small leak accumulates quickly.
3. I have provided all necessary data with my original report to help diagnose and fix this issue, including:
- https://discussions.apple.com/thread/254771724
- https://feedbackassistant.apple.com/feedback/12089791
- Figures
4. I have isolated this to the `configd` process by monitoring memory usage of all system processes over time. `configd` is the only one showing steady growth. A reboot temporarily fixes it, but the leak quickly returns.
Please look into fixing this memory leak issue in `configd` as soon as possible. While new features are exciting, ensuring the stability and performance of core system functions like `configd` should be a top priority. Let me know if you need any additional information from me to properly diagnose and patch this leak.
Thank you
To other Mac users:
You can check this issue by running: sudo vmmap -swapped `pgrep configd`
Best