Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

bosskwei

macrumors member
Original poster
Apr 12, 2023
52
19
The same issues posted at:

Unfortunately, Apple didn't solve these terrible leaks. Yes, Memory Management has always been an issue on any OS (not just Apple's). However,
  1. configd and bluetoothd are daemon processes need to be running 24x7x31.
  2. Apple sells their non-replaceable RAM for a whopping $200/8GB, which should be more responsible to fix memory leak problems.
Feedback (new dump submitted): FB12200609, FB12200601

Stable Reproduction (updated in May 30, 2023):
  • Turn-off the Wi-Fi from control center (top right on your screen)
  • Enable it and wait for auto re-connection
  • Do this again and again, the `configd` goes to eat 200MB+ memory.
Video:
Note that: according to the discussion, this is not a widespread problem, only occurs under certain Wi-Fi conditions (enterprise Wi-Fi AP).
Wi-Fi Setting (Enterprise AP): 802.1X, EAP-PEAP (MSCHAPv2 Authentication), IPv4 with DHCP
Other Observation: The `configd` process need to be running for a seconds, a newly launched one may not occur this issue.

Screenshots:

Screenshot 2023-05-24 at 10.23.40.png


Screenshot 2023-05-24 at 10.17.36.png
Screenshot 2023-05-24 at 10.17.30.png


Workaround:
Bash:
# configd
*/15 * * * * pid=$(pgrep -f '/usr/libexec/configd'); mem=$(top -l 1 -pid $pid | awk '/configd/ {print $8}'); mem=$(echo $mem | sed 's/M$//g'); if [ $mem -gt 512 ]; then kill $pid; fi

# bluetoothd
*/15 * * * * pid=$(pgrep -f '/usr/sbin/bluetoothd'); mem=$(top -l 1 -pid $pid | awk '/bluetoothd/ {print $8}'); mem=$(echo $mem | sed 's/M$//g'); if [ $mem -gt 512 ]; then kill $pid; fi

add this script to root's crontab, it checks `configd` and `bluetoothd` every 15 minutes, and kill any if the memory consumption > 512MB
 

Attachments

  • vmap_configd (700M).txt
    386.9 KB · Views: 128
  • vmap_bluetoothd (500M).txt
    542.7 KB · Views: 222
Last edited:
Thanks for the heads up. It seems it's still too early to "upgrade" to Ventura, even worse if these memory leaks don't get enough attention they won't get fixed even after .6 update so I will probably never update to Ventura, there's literally zero features I personally need.

Get this over to official forums or even better, report it directly to Apple, not here. 👍
 
  • Like
Reactions: zakarhino
activity_monitor.jpg
Holy **** thats bad. I'm still on Monterey. I was just checking this forum again if Ventura is yet viable. I guess not!
Gladly being using Monterey if the quality is on this level. Can more people check if this memory bloat leak is a wider issue on Ventura? Here is a comparison pic from Monterey, i'm running a Macbook Air M1, 16Gig model. Uptime 11 days.
 
Can more people check if this memory bloat leak is a wider issue on Ventura?
Ventura 13.4, plenty of RAM, last booted 7 days ago:
bluetoothd 5.5 MB
configd 5.2 MB

It seems it's still too early to "upgrade" to Ventura, even worse if these memory leaks don't get enough attention they won't get fixed even after .6 update so I will probably never update to Ventura, there's literally zero features I personally need.
There are no systemic memory leaks with Ventura. The last Monterey memory leak (involving search in Finder) was fixed with Ventura.

Yes, people see memory "leaks". When real, they are almost always due some configuration or application issue.

I am sure the OP has a problem, but it is not a widespread one.
 
Ventura 13.4, plenty of RAM, last booted 7 days ago:
bluetoothd 5.5 MB
configd 5.2 MB


There are no systemic memory leaks with Ventura. The last Monterey memory leak (involving search in Finder) was fixed with Ventura.

Yes, people see memory "leaks". When real, they are almost always due some configuration or application issue.

I am sure the OP has a problem, but it is not a widespread one.

99.9% of Mac users are non-tech people, they've never realized what happened in their system.

However, when the 0.1% tech users try to report bugs (with detailed dump) and let others to check, the apple guys say, "There are no systemic memory leaks".
 
However, when the 0.1% tech users try to report bugs (with detailed dump) and let others to check, the apple guys say, "There are no systemic memory leaks".

If 99.9% of users aren't having problems then I would agree that it is not a general or systemic problem. First place to look is at the local configuration. Never had any problems with either of these over the decades I have owned macs, although confess that I never checked their sizes since they weren't a problem. bluetoothd 14.1 MB, configd 6.8 MB on my current system.
 
  • Like
Reactions: kitKAC
If 99.9% of users aren't having problems then I would agree that it is not a general or systemic problem. First place to look is at the local configuration. Never had any problems with either of these over the decades I have owned macs, although confess that I never checked their sizes since they weren't a problem. bluetoothd 14.1 MB, configd 6.8 MB on my current system.
What I meant is, 99.9% of users don't use Activity Monitor.

Anyhow, I'm doing a system re-install (instead of the increamental upgrade) right now, will reply to this thread after 4~5 days.
 
What I meant is, 99.9% of users don't use Activity Monitor.

Anyhow, I'm doing a system re-install (instead of the increamental upgrade) right now, will reply to this thread after 4~5 days.
Running Monterey, I can't find bluetoothd nor configd; are those daemons Ventura's own?
;JOOP!
 
Activity monitor on my Mac Pro and both process are using less than 8MB each; only been running for a day though; will report back in a week or so.
 
I'm running Ventura 13.3.1 (a) and neither configd nor bluetoothd are running on my system. It's been up for 14 days on my MacBook Pro though I see that 13.4 is out so I'll update my MacBook Pro today.
 
I just updated to 13.4 and still don't see the processes. I've updated 2 M1 Macs and they are both running fine. I have my Studio to update next. I tested my production applications and those run fine too.
 
2021 MBP M1Pro:Ventura
configd: 6.4 MB
bluetoothd: 9.3 MB

late 2015 27" iMac i7: Monterey
configd: 2.3 MB
bluetoothd: 4.6

Recently rebooted for the latest updates. Will keep an eye on these processes and update if I see a leak.
 
No issue here:

Ventura 13.4
2023 MacBook Pro 16", uptime 8 days 23:31:

bluetoothd 14.6MB
configd 6.5MB
 
I just updated to 13.4 and still don't see the processes. I've updated 2 M1 Macs and they are both running fine. I have my Studio to update next. I tested my production applications and those run fine too.

Double check whether Activity Monitor is set to display "all processes" or "my processes". I had to switch mine to all in order to see both configd and bluetoothd.
 
  • Like
Reactions: gilby101
Double check whether Activity Monitor is set to display "all processes" or "my processes". I had to switch mine to all in order to see both configd and bluetoothd.

configd is using 5.0 mb and bluetoothd is using 11.1 mb.

So not a problem on my MacBook Pro. I've not really noticed memory leak issues since last year I think.
 
echoing what others have said, this is not an issue on my 14" M1 Pro. That said I've had other issues requiring a reboot
 
configd is using 5.0 mb and bluetoothd is using 11.1 mb.

So not a problem on my MacBook Pro. I've not really noticed memory leak issues since last year I think.
Here, configd is using 4.5 mb and bluetoothd is using 8.0 mb on an M2 MBA 2023.
No issue.
 
My bluetoothd process is 80MB, with my Mac turned on since 5-6 days.

Meanwhile I discovered that Reminders app is using 1,16GB...:confused:
Screenshot 2023-05-28 at 11.11.25.png
 
echoing what others have said, this is not an issue on my 14" M1 Pro. That said I've had other issues requiring a reboot
2021 14" MI Pro on Ventura 13.5 B1, no issues here either:

bluetoothd is using 5.5MB and configd is using 4.7MB.
 
My bluetoothd process is 80MB, with my Mac turned on since 5-6 days.

Meanwhile I discovered that Reminders app is using 1,16GB...:confused:View attachment 2208733

I've had runaway CPU usage in Notes since about 13.3 and my workaround is to move notes to folders and keep the smaller folder open instead of All Notes. Yesterday, I moved a complex note to a folder and the issue went away. I've seen bug reports where having URLs or emojis in the Title can cause this problem. So there may be a bug report open for your problem and maybe a workaround. That said, you might want to start a new thread for your problem as someone else might have a solution or workaround.

I'm going to check my other systems for configd/bluetoothd now.
 
2015 MacBook Pro 15, Monterey 12.6.6, 4.6mb / 2.2 mb, uptime 1 hour
M1 Mini, Ventura 13.4, 13.4 mb / 5.1 mb, uptime 1 day
M1 Studio, Ventura 13.3.1 (a). 21.4 mb / 6.5 mb, uptime 8 days

The higher numbers for the M1 mini and M1 Studio are likely due to Universal Control.

It seems like the vast majority here don't have runaway RAM issues with these two processes. Perhaps you could isolate what triggers the higher use on your system.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.