Apple, please fix memory Leak on `configd` instead of building fancy features

[bosskwei]

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

 

[bosskwei]

Update: I posted this on https://discussions.apple.com/community/mac_os/ventura, and get deleted immediately.

 

[Nermal]

I reported this issue to Apple Support a month ago but have not received a response or acknowledgement yet.

I'm not surprised. It's been about two and a half years since I logged "here's how to crash the OS to the point that you need to cut the power to recover" and it hasn't had a single comment yet.

 

[gilby101]

How do your screenshots relate to memory use by configd?

My configd is right now using 3.2 MB and this Mac has not been rebooted for 9 days. I am not sure whether you have something specific to your Mac or just an imagined issue.

 

[chrfr]

On my Mac mini that hasn't been rebooted in 5 days, 20 hours, configd is using 6MB and installd is using 6.5MB.
On an iMac Pro that hasn't been restarted in 13 days, 19 hours, configd is using 4.2MB and installd is using 57.8MB.
I'm not convinced this is an actual bug in the OS.
Also, iOS doesn't support swap so there's no risk of damaging storage from memory use. iPads with M1/M2 can support swap but lower models do not.

 

[bosskwei]

On my Mac mini that hasn't been rebooted in 5 days, 20 hours, configd is using 6MB and installd is using 6.5MB.
On an iMac Pro that hasn't been restarted in 13 days, 19 hours, configd is using 4.2MB and installd is using 57.8MB.
I'm not convinced this is an actual bug in the OS.
Also, iOS doesn't support swap so there's no risk of damaging storage from memory use. iPads with M1/M2 can support swap but lower models do not.

This issue seems related to power manager, let's see if any MacBook user who usually plugs in and out, is facing the same trouble

 

[bosskwei]

How do your screenshots relate to memory use by configd?

My configd is right now using 3.2 MB and this Mac has not been rebooted for 9 days. I am not sure whether you have something specific to your Mac or just an imagined issue.

Yes it's just screenshots, but if you can let apple open source their system, I may just point out where the problem comes from. let's see if any MacBook user who usually plugs in and out, is facing the same trouble.

 

[bosskwei]

How do your screenshots relate to memory use by configd?

My configd is right now using 3.2 MB and this Mac has not been rebooted for 9 days. I am not sure whether you have something specific to your Mac or just an imagined issue.

Appended with two configd samples, in your word, it's just editable txt files, and maybe forged by me.

 

[chrfr]

This issue seems related to power manager, let's see if any MacBook user who usually plugs in and out, is facing the same trouble

Ok, on this 2023 14" M2 Pro Macbook Pro that's been up for 5 days, 5 hours, configd is using 6.3MB and installd 5.9MB.

 

[MacMan988]

Pretty much all the bugs I have had to face in MacOS for the last few years are still there.
I'd say, don't have high expectation in the bug fixes department from Apple.
I guess they are busy brushing up aluminum or something most of the time.

 

[HDFan]

It's been about two and a half years since I logged "here's how to crash the OS to the point that you need to cut the power to recover"

Any idea what triggered the memory leak? I've never experienced the problem.

 

[Slartibart]

what about killing configd, restarting it with the -v flag and then see wether the console log as well as the configd bundles and plist files in SystemConfiguration may provide some more hints as to what is going on and why on on your system?
You mention that you traced it down to the power management on your Macbook - like to share some details on that? Additionally: What M-model Macbook are you using? Which Ventura version?

 

[bosskwei]

Update: attach file "Sample of configd (250M).txt", this dump / sample is generated by Activity Monitor

 

[bosskwei]

Any idea what triggered the memory leak? I've never experienced the problem.

My platform is Macbook Air M2, this issue usually happens after booting for 4+ days. It seems also related to power manager (?), when I plug-out my mac and then walking to my office, configd may eat 70M+ memory

 

[bosskwei]

Update: attach file "Sample of configd (250M).txt", this dump / sample is generated by Activity Monitor

+ "vmmap dump (250M).txt"

 

[bosskwei]

what about killing configd, restarting it with the -v flag and then see wether the console log as well as the configd bundles and plist files in SystemConfiguration may provide some more hints as to what is going on and why on on your system?
You mention that you traced it down to the power management on your Macbook - like to share some details on that? Additionally: What M-model Macbook are you using? Which Ventura version?

Thanks for your attention. I've just realize this:

```
/System/Library/SystemConfiguration/IPConfiguration.bundle/Contents/MacOS/IPConfiguration
Dispatch continuations 103000000-107000000 [ 64.0M 176K 176K 16K] rw-/rwx SM=PRV
MALLOC_TINY 145600000-145700000 [ 1024K 64K 64K 960K] rw-/rwx SM=PRV DefaultMallocZone_0x1029d0000
MALLOC_TINY 145700000-145800000 [ 1024K 48K 48K 976K] rw-/rwx SM=PRV DefaultMallocZone_0x1029d0000
MALLOC_TINY 145800000-145900000 [ 1024K 96K 96K 928K] rw-/rwx SM=PRV DefaultMallocZone_0x1029d0000
```

Maybe it is related to "IPConfiguration"? There are lots of "MALLOC_TINY"

 

[bosskwei]

Thanks for your attention. I've just realize this:

```
/System/Library/SystemConfiguration/IPConfiguration.bundle/Contents/MacOS/IPConfiguration
Dispatch continuations 103000000-107000000 [ 64.0M 176K 176K 16K] rw-/rwx SM=PRV
MALLOC_TINY 145600000-145700000 [ 1024K 64K 64K 960K] rw-/rwx SM=PRV DefaultMallocZone_0x1029d0000
MALLOC_TINY 145700000-145800000 [ 1024K 48K 48K 976K] rw-/rwx SM=PRV DefaultMallocZone_0x1029d0000
MALLOC_TINY 145800000-145900000 [ 1024K 96K 96K 928K] rw-/rwx SM=PRV DefaultMallocZone_0x1029d0000
```

Maybe it is related to "IPConfiguration"? There are lots of "MALLOC_TINY"

Update: this new discovery is sent to Apple (FB12141011)

 

[Slartibart]

you allow configd in your firewall? you run a antivirus proxy, VPN…?

 

[bosskwei]

you allow configd in your firewall? you run a antivirus proxy, VPN…?

No firewall, no antivirus, sometimes using L2TP VPN. (will observe if it is related to VPN)

 

[bogdanw]

You can check this issue by running: sudo vmmap -swapped `pgrep configd`

Have you tried to disable swap?

 

[bosskwei]

Have you tried to disable swap?

No. It has nothing to do with swap in this case.

 

[bogdanw]

No. It has nothing to do with swap in this case.

How do you know it has nothing to do with virtual memory?

 

[bosskwei]

How do you know it has nothing to do with virtual memory?

Hi, in my understanding, when the memory footprint is below physical memory limitation, the system actually doesn't do a swap, but some untouched but allocated memory will be marked as 'compressed', 'swapable'. So that I mentioned it has nothing to do with swap.

This issues is observed on Macbook Air M2, 16G+1T model, with the latest system installed: Ventura 13.3.1.

```
Process: configd [26632]
Path: /usr/libexec/configd
Identifier: configd
Version: ???
Code Type: ARM64
Platform: macOS
Parent Process: launchd [1]

Date/Time: 2023-04-24 18:02:30.508 +0800
Launch Time: 2023-04-21 14:00:01.283 +0800
OS Version: macOS 13.3.1 (22E261)
Report Version: 7
Analysis Tool: /Applications/Xcode.app/Contents/Developer/usr/bin/vmmap
Analysis Tool Version: Xcode 14.3 (14E222b)
```

 

[bogdanw]

Hi, in my understanding, when the memory footprint is below physical memory limitation, the system actually doesn't do a swap, but some untouched but allocated memory will be marked as 'compressed', 'swapable'. So that I mentioned it has nothing to do with swap.

Shouldn't that read as swapped_out=0K(0%), you have swapped_out=267.6M(37%)

 

[bosskwei]

Shouldn't that read as swapped_out=0K(0%), you have swapped_out=267.6M(37%)

To clarify, swap function is enabled as system default (never touch sip). So that these `swapped out` didn't really flush to on-disk swap files. Physical memory usage ~70%, something like `top`:
```
4272M framework vsize, 0(0) swapins, 0(0) swapouts.
```

From my understanding, these swaps exist as compressed memory blocks and are kept in DRAM.