Roadmap: [Docker Desktop] Investigate Mac CPU performance
Tell us about your request
CPU performance on Mac is a long standing issue, we have investigated this in the past but want to dedicate time to re-invetsigate this and try and find a fix
Which service(s) is this request for?
Desktop
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We keep spiking to 100% CPU and this isn't good, no one likes their laptop taking off
Are you currently working around this issue?
N/A
Additional context
N/A
Attachments
https://github.com/docker/for-mac/issues/1759
https://github.com/docker/for-mac/issues/3499
https://github.com/docker/for-mac/issues/2601
nebuk89
All 119 comments
Ben, for purposes of documentation of pain points with Docker on Mac, I wanted to make sure there was a reference back to these complaints.
https://github.com/docker/for-mac/issues/3499
Thanks -Alan
aguedeney
on 4 Apr 2020
Please add docker/for-mac#4392 to this list.
cculianu
on 4 Apr 2020
Thanks @aguedeney and @cculianu - when we move this into in progress I will link back the tickets we are using in for-mac to highlight where we will be discussing with everyone and also where we will be seeking fresh logs for issues :) please feel free to add other cases here as you think appropriate!
nebuk89
on 6 Apr 2020
Please add docker/for-mac#4064.
schellj
on 14 Apr 2020
The primary issue with CPU that I have seen relates to volume mounts, transfused, and heavy IO workloads. I have observed this a lot of times and inside the VM it is usually transfused using the CPU.
See this on why mounts use lots of CPU. Namely:
A Linux system call such as open or read that accesses bind-mounted files in a container must be. - turned into a FUSE message in the Linux VFS - proxied over a virtio socket by transfused - forwarded onto a UNIX domain socket by HyperKit - deserialized, dispatched and executed as a macOS system call by osxfs The entire process then takes place in reverse to return the result of the macOS system call to the container.
mc0
on 7 May 2020
See this on why mounts use lots of CPU.
This definitely makes sense for bind mounts because it's having to go in and out of the VM to interface with the host filesystem, but I'm still seeing high CPU usage after we switched to using named volumes and that should all be inside of the VM, but I'm still seeing high CPU usage when things are sitting idle, so is there any similar :cached/:delegated tags for named volumes to help with performance issues there?
daveisfera
on 7 May 2020
This issue is too broad. Some people may suffer from mounts CPU performance, but other have 100% cpu after prune command in this issue: https://github.com/docker/for-mac/issues/4064
m8rge
on 8 May 2020
Thanks to all the responses!
We will start our investigation on this in the next ~2 weeks!
Watch out for incoming questions on some of the for-mac issues. We won't respond to posts in here with logs etc but will use this to share updates as we make progress :)
nebuk89
on 11 May 2020
Hope this helps in some way.
I was running into CPU issues as well and noticed something weird happening with volumes.
I created three volumes in my compose file, one for the project directory, one to ignore node_modules, and another to mount a specific node_module.
It works as expected, a file from the specific node_module that I modified locally was copied to the container. Likewise I modified a file in another node_module and the change was not copied to the container. Everything works fine.
The issue came when I did a docker-compose restart, the other node_module that should have been ignore was copied into the container, and my laptop fans were taking off. Every file in node_modules after that point was copied over to the container even though I specified it not to.
I did investigating a few months ago so the reproduction steps might be off, but there was definitely an issue with volumes copying files that it was not supposed to.
- volumes
- ./:/src
- /src/node_modules
- ./node_modules/express:/src/node_modules/express
alechirsch
on 16 May 2020
I would like to highlight that https://github.com/docker/for-mac/issues/3499#issuecomment-623960890 has a concrete suspicion of potentially bugged code that might be easy to investigate (with OCAML knowledge).
The primary issue with CPU that I have seen relates to volume mounts, transfused, and heavy IO workloads. I have observed this a lot of times and inside the VM it is usually transfused using the CPU.
I would also like to add that this is not the only cause. I do sometimes see docker spike to at remain at 100% without any containers running. Definitely no high IO workload in that case, pure "home" usage.
andig
on 4 Jun 2020
I've also had times where the Docker process was using 100% CPU indefinitely when no containers were running.
schellj
on 4 Jun 2020
@schellj , can you do a diagnose when it happens? (if the whale menu is responding of course).
I you cannot use the UI, you can still do it with cli command:
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather -upload
ebriney
on 18 Jun 2020
@ebriney I haven't had any issues with Docker for Mac using a lot of CPU unexpectedly since early May - see https://github.com/docker/for-mac/issues/4064#issuecomment-625293060, but I did a couple of diagnostics when I was - see https://github.com/docker/for-mac/issues/4064#issuecomment-574391283 and https://github.com/docker/for-mac/issues/4064#issuecomment-574431375 (I made some other relevant comments in that issue as well).
schellj
on 18 Jun 2020
I installed the edge build (with spindump) and uploaded this diagnostic:
0D3FCEE0-663F-4A5E-8DA2-1B79B6746B54/20200626175354
The Kubernetes containers were running (with nothing to manage), nothing from my side, and Docker used 50% CPU.
haslo
on 26 Jun 2020
My Diag Id with spindump 80E081FA-7763-4245-BB3F-15814B31E0BB/20200627174556
m8rge
on 27 Jun 2020
Another diag ID F2F1BBBF-4BF7-4158-BCFA-0C29469D1E33/20200630084358
joerobot
on 30 Jun 2020
Here's another one with only 5-10% but it still seems like a lot with no containers running on a decent MBP: A913E1F9-1085-4C2B-A79D-4B6862C0EA1E/20200630095026
andig
on 30 Jun 2020
Another diag C39B37CE-DA64-46FE-B4ED-3A714CE9CC62/20200701075247 with spindump version.
Using Big Sur but I feel no differences from Catalina…
xjrcode
on 1 Jul 2020
Another diag: 93B23EAA-7413-4ACB-8278-F008093AD412/20200701154406
I don't think I'm using spindump version, still reading up on this ticket, but my mac is about to take off and I've had a number of crashes lately. I suspect that they're related to docker, but that's just a guess on my part.
mikepflu
on 1 Jul 2020
Thanks for those reports, will compute them and see what we can get from them
ebriney
on 2 Jul 2020
We've managed to repro one source of unexpected high CPU in hyperkit and com.docker.osxfs by
- checking out a large .js project on the host (https://github.com/microsoft/vscode)
- sharing the code with a container
docker run -v ~/vscode:/anywhere alpine sh - on the host: building the project with
yarn install
The build generates a lot of file events which are all injected into the VM.
Unfortunately there are so many file events generated, it takes a long time for them to be fully processed. The build finishes quickly but hyperkit and com.docker.osxfs remain busy for a very long time.
We have an experimental prototype build which we believe fixes this particular problem, if you'd like to try it. The build is based on Edge and can be downloaded from https://desktop-stage.docker.com/mac/edge/46421/Docker.dmg . The build does 3 things to improve performance:
- events are batched, rather than injected one-by-one
- if the event queue starts to become full, it will prioritise cache invalidations and drop inotify event injections (since inotify events are expensive to create)
- if more than 1000 events are pending, it will give up, drop all the events and invalidate all caches instead.
If you have a chance to try it, let us know what happens! Note that this is an experimental build and won't work with existing containers -- they will need to be re-created. It might be necessary to reset to factory defaults before and after using this build.
djs55
on 2 Jul 2020
I can live with docker containers using a lot of CPU for some reason though, it's not great but at least I'm working with Docker at that time and I'm expecting it to do something.
The fact that Docker suddenly starts using 100-150% CPU without any running containers is particularly disturbing.
If I have background service loaded, I really want to be able to trust that this service won't interfere with my work when I'm not using it.
It usually takes a while before I connect the dots between my laptop going in overdrive, getting very hot and draining battery very fast, and checking if Docker has gone mad again.
Is there any command I can run to verify in which part of the code the CPU is spinning when this happens again?
I'm kind of surprised this issue has existed for such a long time, I guess the devs are unable to reproduce it?
Doing some kind of profiling on the process should make it pretty clear what's going on right?
I'll definitely run the command above if this happens again. If you have any other tips for how I can help out, please let me know! Potentially running strace or something?
dietervdw-spotify
on 2 Jul 2020
@dietervdw-spotify I think there are several different performance issues which look similar.
- if the CPU is used by
com.docker.hyperkitandcom.docker.osxfsthen the problem probably relates to file sharing. The build in https://github.com/docker/roadmap/issues/12#issuecomment-652894544 attempts to fix this - if the CPU is used only by
com.docker.hyperkitthen there's something else inside the VM using CPU. It's possible to dig in withdocker run -it --privileged --pid=host justincormack/nsenter1and then runtop - if the CPU is used by the
Dockerprocess on the Mac, this is a problem in the UI itself
@PhilETaylor could you log into the VM and see which process (if any) is spinning? Use docker run -it --privileged --pid=host justincormack/nsenter1 and then top
djs55
on 2 Jul 2020
for me historically, and today, top is always /usr/bin/lifecycle-server - this screenshot during heavy build work
PhilETaylor
on 2 Jul 2020
and now with no docker containers running:
PhilETaylor
on 2 Jul 2020
@PhilETaylor thanks for the top screenshot. With no containers running it looks like the processes inside the VM aren't busy -- the Linux VM reports 98% idle. I think this suggests a problem with the hypervisor process itself. Could you try running sudo dtruss -p <hyperkit pid> to see what system calls it is making? (From this comment https://github.com/docker/for-mac/issues/3499#issuecomment-628880539 ). If there are a lot of read calls returning -1 then the experimental hyperkit here might fix it: https://github.com/docker/for-mac/issues/3499#issuecomment-640113288
Are you running a tool called osquery? There seems to be a clash between Docker and it, see https://github.com/docker/for-mac/issues/3499#issuecomment-639140844
djs55
on 2 Jul 2020
With no containers (apart from justincormack/nsenter1 running top)
PhilETaylor
on 2 Jul 2020
Some of these in the dtruss too
PhilETaylor
on 2 Jul 2020
Using docker-compose with 4 projects (node apline images) using file watch over thousands of files (two projects with angular + 2 prjects with NetsJs)
With this build com.docker.osxfs is at 0% and hyperkit is about 70-80% of 400% when images are on iddle. I think this is a big improvement. Thank you!
xjrcode
on 2 Jul 2020
We get various reports that hyperkit has high CPU even when no containers are running. But one thing I'm not sure about: does anyone have high CPU without having run any containers since last reboot? Or is it only if you have previously run containers and then stopped them but the CPU still continues? These would likely have different causes.
stephen-turner
on 2 Jul 2020
And to answer @dietervdw-spotify's point: you're right, we can't reproduce the problems. We suspect it's only a small proportion of users, but still a high number in absolute terms given our millions of users.
stephen-turner
on 2 Jul 2020
@stephen-turner : Completely understand, that's tricky. I'm not 100% sure how you can profile a process on MacOSX, but if you know how to do this I'd be happy to try to get some more info the next time this happens!
dietervdw-spotify
on 2 Jul 2020
@dietervdw-spotify if you have the PID of the process you might try:
sample PID 60 1 -file ~/Desktop/DockerSample.txt
you have to insert the PID of the particular Docker process. lets say the process is 582 you would write:
sample 582 60 1 -file ~/Desktop/DockerSample.txt
that would sample process 582 for 60 seconds with 1 milliseconds of runtime between samples and the output would be written to the desktop into the DockerSample.txt file
p.s. in case sample isn't available and you haven't installed Xcode it might be necessary to install the command line tools: https://osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x/ (I am not entirely sure anymore if sample is already available without them)
rpkoller
on 2 Jul 2020
@stephen-turner
But one thing I'm not sure about: does anyone have high CPU without having run any containers since last reboot?
For me, hyperkit had high CPU usage after a machine reboot without starting any containers.
The 'edge' release mentioned earlier https://github.com/docker/roadmap/issues/12#issuecomment-652894544 so far has fixed that problem.
matonb
on 3 Jul 2020
It appears that enabling kubernetes in preferences causes the problem for me.
Docker Desktop 2.3.3.0 (46421), Channel edge
Engine 19.03.12
Notary: 0.6.1
Compose: 1.26.1
Cred. Helper: 0.6.3
Kubernetes v1.18.3
OS: Catalina 10.15.5
From a fresh boot, no containers started:
Without enabling kubernetes, everything is basically idle:
After enabling kubernetes:
Simply disabling kunernetes after it's started doesn't reduce the CPU usage much:
matonb
on 3 Jul 2020
I can’t guarantee it was caused by it (and have since left the company so hard to recreate it), but we had a fairly large Rails app, with some React JS as well.. but the only thing part running in docker to my knowledge) was a PostgreSQL database, that used a volume (I think?) for its DB files. I couldn’t say when it started for sure, but I’m wondering if it may have been after running the tests suite, which would create/tear down a lot of things in the DB (and presumably thus cause a lot of disk writes?)
If others have noticed a similar situation, and it seems unique enough from other tests tried here, I wonder if it would be possible to put together a minimal example test case?
—
On a completely different line of thinking, I wonder if it would be possible to add a ‘usage monitor’ type watching code inside docker itself, that could notice and send some feedback to the docker team when something like this happens in the wild (to get better sample cases/etc)
0xdevalias
on 3 Jul 2020
@matonb Thanks, this is good information. There are two things I picked out of it:
1) We know that Kubernetes can be a problem. Unfortunately the problem is upstream, and other desktop Kubernetes distributions have the same issue with CPU.
2) It's interesting that the problem doesn't go away when you turn Kubernetes off again. But in fact turning on Kubernetes does create some containers, so that suggests that it's the same bug that @djs55 has fixed where there are too many file system events backed up. This would be worse if Kubernetes generates an excessive number of events. It's good that you found that @djs55's patch fixed it.
stephen-turner
on 3 Jul 2020
So does anyone else have an example with no containers running, no containers having run since Docker was started, and Kubernetes turned off?
stephen-turner
on 3 Jul 2020
So does anyone else have an example with no containers running, no containers having run since Docker was started, and Kubernetes turned off?
I can test that theory over the weekend. Its not often I reboot my mac's, ever ;-) I don't use Kubernetes so its always off.
And to answer @dietervdw-spotify's point: you're right, we can't reproduce the problems. We suspect it's only a small proportion of users, but still a high number in absolute terms given our millions of users.
I must be unlucky then, as my work iMac (expensive) my home iMac (midrange) and my MacBook Pro all exhibit this from time to time. Happy to provide whatever is needed to debug.
PhilETaylor
on 3 Jul 2020
So does anyone else have an example with no containers running, no containers having run since Docker was started, and Kubernetes turned off?
I used to be plagged with high CPU with no kube ever setup , very few number of images locally, and never building one.
i would only run a couple of them daily.
but since i've moved to edge i have not seen the issue.
FernandoMiguel
on 3 Jul 2020
Client: Docker Engine - Community
Azure integration 0.1.4
Version: 19.03.12
API version: 1.40
Go version: go1.13.10
Git commit: 48a66213fe
Built: Mon Jun 22 15:41:33 2020
OS/Arch: darwin/amd64
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 19.03.12
API version: 1.40 (minimum version 1.12)
Go version: go1.13.10
Git commit: 48a66213fe
Built: Mon Jun 22 15:49:27 2020
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: v1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Client:
Debug Mode: false
Plugins:
app: Docker Application (Docker Inc., v0.8.0)
buildx: Build with BuildKit (Docker Inc., v0.3.1-tp-docker)
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 5
Server Version: 19.03.12
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.19.76-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.453GiB
Name: docker-desktop
ID: RZWF:CQX4:UJEU:SU6Z:3V2G:YT4A:FMQV:742L:GOY5:HU4L:KKAS:QXQJ
Docker Root Dir: /var/lib/docker
Debug Mode: true
File Descriptors: 41
Goroutines: 48
System Time: 2020-07-03T12:03:28.3182982Z
EventsListeners: 3
HTTP Proxy: gateway.docker.internal:3128
HTTPS Proxy: gateway.docker.internal:3129
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.6
BuildVersion: 19G46c
@djs55 I can confirm that the build fixes the problem for me. I previously saw persistent high CPU usage for com.docker.hyperkit and com.docker.osxfs when running a fastapi container. Tweaking options, rebooting, etc. didn't seem to help anything. CPU usage was low without any running containers, or only running containers without volumes mounted (postgres and redis).
Since I started running the new build yesterday, com.docker.hyperkit hovers in the teens % CPU and com.docker.osxfs 0 when running the same fastapi container.
adeolonoh
on 3 Jul 2020
@djs55 confirmed the edge build reference in https://github.com/docker/roadmap/issues/12#issuecomment-652894544 dramatically reduced CPU utilization on com.docker.hyperkit.
blazindrop
on 6 Jul 2020
@djs55 confirmed the edge build reference in #12 (comment) dramatically reduced CPU utilization on com.docker.hyperkit.
Same for me 👍
TomOMara
on 6 Jul 2020
@djs55 confirmed the edge build reference in #12 (comment) dramatically reduced CPU utilization on com.docker.hyperkit.
I can also confirm this is making a huge difference in reducing CPU usage.
TehNrd
on 7 Jul 2020
For me unfortunately it didn't change anything. For the record at the time I took the screenshot I wasn't doing anything in the container I only started it like 10 minutes ago and didn't touch it at all.
chnbz
on 7 Jul 2020
Hello, just a short input, in my case it did dramatically lower the %cpu usage however when debugging (xdebuger with php) it would not see my code changes until i restarted the whole container which is a show stopper.
sinnayman
on 7 Jul 2020
Running 2.3.2.0 (46268) and still seeing relatively high cpu utilization ~50% for an otherwise (nearly) idle vm. K8s is enabled with only system containers running - when we refer to the upstream issue are we referring to kubernetes/kubernetes#75565 ?
It still looks like a hyperkit issue to me - who could take a closer look? Took an initial sample
HarryWeppner
on 7 Jul 2020
Yes, that is the upstream issue. It manifests as Hyperkit CPU but is an upstream issue.
stephen-turner
on 7 Jul 2020
@stephen-turner has anyone investigated this as a hyperkit issue? In principle, I'd classify it as an hypervisor issue if a nearly idle guest burns host cpu cycles needlessly.
HarryWeppner
on 7 Jul 2020
It's not idle, that's the problem, Kubernetes is really busy, including with filesystem events that cross the hypervisor boundary. You're right in one sense, because that's much more expensive for a hypervisor than if you can read the filesystem directly as on Linux. But it's not just hyperkit, Kube distros built on other hypervisors have the same problem.
stephen-turner
on 7 Jul 2020
So does anyone else have an example with no containers running, no containers having run since Docker was started, and Kubernetes turned off?
I have no container running. Kubernetes is disabled. Just started docker and have 100% cpu. Have docker desktop version 2.3.2.0 (46292)
80E081FA-7763-4245-BB3F-15814B31E0BB/20200707173508
m8rge
on 7 Jul 2020
We've managed to repro one source of unexpected high CPU in
hyperkitandcom.docker.osxfsby
- checking out a large .js project on the host (https://github.com/microsoft/vscode)
- sharing the code with a container
docker run -v ~/vscode:/anywhere alpine sh- on the host: building the project with
yarn installThe build generates a lot of file events which are all injected into the VM.
Unfortunately there are so many file events generated, it takes a long time for them to be fully processed. The build finishes quickly but
hyperkitandcom.docker.osxfsremain busy for a very long time.We have an experimental prototype build which we believe fixes this particular problem, if you'd like to try it. The build is based on Edge and can be downloaded from https://desktop-stage.docker.com/mac/edge/46421/Docker.dmg . The build does 3 things to improve performance:
- events are batched, rather than injected one-by-one
- if the event queue starts to become full, it will prioritise cache invalidations and drop inotify event injections (since inotify events are expensive to create)
- if more than 1000 events are pending, it will give up, drop all the events and invalidate all caches instead.
If you have a chance to try it, let us know what happens! Note that this is an experimental build and won't work with existing containers -- they will need to be re-created. It might be necessary to reset to factory defaults before and after using this build.
Is better now, but not ideal. Thanks man!
gustavorglima
on 7 Jul 2020
@stephen-turner do you have an hypothesis what filesystem events these are specifically?
Fyi, @mc0 has done an excellent job documenting his tweaks on minikube as part of kubernetes/minikube#3207. After implementing these tweaks on Docker Desktop the "idle" host CPU usage is now hovering around 21% - an improvement but still wasteful.
Note: in my experiment I simply edited the resource manifests in /var/lib/kubeadm/manifests.
HarryWeppner
on 8 Jul 2020
So does anyone else have an example with no containers running, no containers having run since Docker was started, and Kubernetes turned off?
I have no container running. Kubernetes is disabled. Just started docker and have 100% cpu. Have docker desktop version 2.3.2.0 (46292)
80E081FA-7763-4245-BB3F-15814B31E0BB/20200707173508
Thanks @m8rge, we'll have a look.
stephen-turner
on 8 Jul 2020
@stephen-turner do you have an hypothesis what filesystem events these are specifically?
Fyi, @mc0 has done an excellent job documenting his tweaks on minikube as part of kubernetes/minikube#3207. After implementing these tweaks on Docker Desktop the "idle" host CPU usage is now hovering around 21% - an improvement but still wasteful.
I haven't looked into it closely, but I assume they're the same ones discussed in that minikube ticket.
We will try @mc0's config changes, thank you for the pointer. It looks like they will make some difference, although I notice that he still says that kubernetes/kubernetes#89936 is a blocker and that he still found the CPU usage so high that his team stopped using minikube. ☹️
stephen-turner
on 8 Jul 2020
Not sure what's different today but com.docker.hyperkit is consistently high in utliization again even on Edge.
No containers running.
Partial spindump (only hyperkit for censorship :))
https://gist.github.com/blazindrop/73a8d3cd3e96cddc3bed484114eefea8
~ 10 seconds of output from "sudo dtruss -a -p 21366 -c -d":
CALL COUNT
writev 3
psynch_cvclrprepost 4
readv 6
write 11
select 18
psynch_mutexdrop 19
psynch_mutexwait 19
psynch_cvsignal 155
psynch_cvwait 203
kevent 18796
read 18798
blazindrop
on 9 Jul 2020
Thanks @blazindrop, are you still using the private build that @djs55 posted in https://github.com/docker/roadmap/issues/12#issuecomment-652894544 or are you on a released version of Edge?
stephen-turner
on 9 Jul 2020
@stephen-turner @djs55 Thanks for fix! While testing I've spotted that the new file with tty path created by 2.3.3.0 version had zero privileges. https://github.com/moby/hyperkit/pull/291
kelvich
on 10 Jul 2020
Still experiencing 50% CPU usage across the following builds:
- the private build posted above ie: Docker 2.3.3.0 (46421) Edge with Kubernetes v1.18.3, and have made sure not to upgrade to the latest Edge version.
- latest edge, ie: Docker 2.3.3.0 (46574) Edge with Kubernetes v1.18.3.
- latest stable, ie: Docker 2.3.0.3 (45519) Stable with Kubernetes v1.16.5.
I've given the VM 4G RAM, 1GB swap.
After a factory reset, com.docker.hyperkit on the host uses ~5% CPU .
When I enable Kubernetes, com.docker.hyperkit CPU jumps to 50%. No running pods.
Using justincormack/nsenter1 to enter the the VM, I see CPU is idle but there's regular I/O:
$ iostat -d -c -z -m
Linux 4.19.76-linuxkit (docker-desktop) 07/11/20 _x86_64_ (6 CPU)
avg-cpu: %user %nice %system %iowait %steal %idle
1.50 0.00 1.71 0.08 0.00 96.71
Device: tps MB_read/s MB_wrtn/s MB_read MB_wrtn
vda 18.05 0.00 1.16 3 1606
vda1 12.83 0.00 1.16 2 1606
sr0 1.86 0.14 0.00 194 0
sr1 0.01 0.00 0.00 0 0
sr2 1.40 0.10 0.00 143 0
I've enabled Kubernetes -> Show system containers. On the host I see the k8s API server is using the most CPU:
$ docker stats --format "table {{printf \"%.25s\" .Name}}\t{{.CPUPerc}}\t{{.MemUsage}}\t{{.NetIO}}\t{{.BlockIO}}" --no-stream
NAME CPU % MEM USAGE / LIMIT NET I/O BLOCK I/O
k8s_compose_compose-78f95 0.09% 8.324MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_vpnkit-controller_vpn 0.00% 15.78MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_compose_compose-api-6 0.20% 24.14MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_storage-provisioner_s 0.40% 7.383MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_compose-78f95d4f8 0.00% 324KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_compose-api-6ffb8 0.00% 288KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_vpnkit-controller 0.00% 340KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_storage-provision 0.00% 296KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_coredns_coredns-5644d 0.61% 7.309MiB / 170MiB 0B / 0B 0B / 0B
k8s_coredns_coredns-5644d 0.59% 7.562MiB / 170MiB 0B / 0B 0B / 0B
k8s_kube-proxy_kube-proxy 0.06% 9.938MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_coredns-5644d7b6d 0.00% 352KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_coredns-5644d7b6d 0.00% 320KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_kube-proxy-2kwlf_ 0.00% 300KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_kube-controller-manag 2.50% 34.84MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_kube-apiserver_kube-a 6.88% 359.6MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_etcd_etcd-docker-desk 2.96% 27.32MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_kube-scheduler_kube-s 0.08% 11.62MiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_kube-controller-m 0.00% 324KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_kube-apiserver-do 0.00% 324KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_etcd-docker-deskt 0.00% 308KiB / 3.848GiB 0B / 0B 0B / 0B
k8s_POD_kube-scheduler-do 0.00% 312KiB / 3.848GiB 0B / 0B 0B / 0B
tekumara
on 11 Jul 2020
Diagnostic ID: CD36DE77-20DF-41D0-A81D-843353BC1904/20200713081915
- average CPU usage 130% for about two hours right after a system boot
- no containers running
- activated Kubernetes, disabeld local cluster after start
- CPU usage dropped to ~40% right after the diagnosis finished 🤔 and then occasionally spiked towards 100%
panzerfahrer
on 13 Jul 2020
Thanks @blazindrop, are you still using the private build that @djs55 posted in #12 (comment) or are you on a released version of Edge?
I'm still on the version @djs55 posted in #12. Today my CPU fan is mostly idle I'll update the Edge version and monitor.
blazindrop
on 14 Jul 2020
I can also confirm this is making a huge difference in reducing CPU usage.
I spoke too soon. Still seeing huge CPU usage, 250%+.
2.3.3.0 (46574) edge
Kubernetes disabled.
Update:
I originally installed the release in https://github.com/docker/roadmap/issues/12#issuecomment-652894544and the issue seemed resolved but after a few days I was prompted to install an update. The update installed the version above, 2.3.3.0 (46574). Removing 2.3.3.0 (46574) edge and then reinstalling 2.3.3.0 (46421) seems to have fixed it. Perhaps the changes in 46421 were not yet merged into 46574?
TehNrd
on 14 Jul 2020
Thanks @TehNrd , no, some patches are not in the last published edge release, we hope to put all of them in the next one.
ebriney
on 15 Jul 2020
It's doing it again, version 2.3.0.3 . ~140% CPU, no containers running.
Mac OSX sample of process here.
A few minutes of sudo dtruss -a -p 21366 -c -d:
CALL COUNT
kevent_id 2
psynch_mutexwait 22797
psynch_mutexdrop 22818
workq_kernreturn 458394
~I won't kill the process for the coming hours (and hope my laptop doesn't melt), if you want me to do any more debugging, please contact me ASAP.~ Sorry couldn't let my poor laptop suffer any longer.
Output of instruments -l 30000 -t Time\ Profiler -p 14645
Output of sample 14645 30 -file
Interesting outtakes:
dietervdw-spotify
on 15 Jul 2020
So does anyone else have an example with no containers running, no containers having run since Docker was started, and Kubernetes turned off?
@stephen-turner
I did the following:
- Uninstalled Docker.
- Reinstalled the edge build referenced above (see screenshot for versions).
- Rebooted.
In the screenshots below you can see that there are no containers, no images, and I have not attempted to use Docker at all, except for running docker ps -a and docker image ls -a. CPU still averages over 100% for com.docker.hyperkit.
nm777
on 17 Jul 2020
@nm777 Great, thanks, could you please generate diagnostics when it's in this state and paste the id here?
stephen-turner
on 17 Jul 2020
@nm777 Great, thanks, could you please generate diagnostics when it's in this state and paste the id here?
@stephen-turner Here is the diagnostic ID: CD9B3F06-3EB1-49D9-AAFF-9E7CA3304F30/20200717203851
nm777
on 17 Jul 2020
@stephen-turner Please forgive the bugspam but I just want to thank docker for taking the time to look into this again as a priority. My company embraced docker very early on for our production (2016) and development (2014) workloads and this Mac CPU/IO issue is singlehandedly causing us to look for alternatives to running a local k8s cluster in development. It's just one of those things that makes working in the system an absolute nightmare. Thx!
michaelfavia
on 18 Jul 2020
@m8rge I've taken a look in the diagnostics you provided in https://github.com/docker/roadmap/issues/12#issuecomment-655016830 . I observe that:
- the processes in the VM have not consumed (virtual) CPU
- the
com.docker.hyperkitis consuming > 100% CPU
I think this could be the clash between osquery and com.docker.hyperkit. Could you try to reproduce with a later version? Version 2.3.3.2 was released yesterday: https://desktop.docker.com/mac/edge/46784/Docker.dmg
djs55
on 22 Jul 2020
@panzerfahrer thanks for your diagnostic in https://github.com/docker/roadmap/issues/12#issuecomment-657404017 above. I observe that the process taking most CPU is:
PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
1054 139.8 0.3 5014960 52156 ?? R 8:08AM 172:23.89 /Applications/Docker.app/Contents/MacOS/Docker
This is the process responsible for managing the system configuration, starting the other processes and populating the whale menu. Unfortunately I can't tell from the logs what caused this. I have 2 suggestions
if you want to stick with stable and it happens again, use "Activity Monitor", click on this process, click on the (i) symbol; click on the "Sample" button and cut and paste the trace here. Hopefully it will help highlight where in the code it's spinning
if you're happy to switch to edge, there was a bug fixed recently which could cause that process to spin. It's worth trying the latest edge https://desktop.docker.com/mac/edge/46784/Docker.dmg to see if that works any better.
djs55
on 22 Jul 2020
@nm777 thanks for your diagnostic in https://github.com/docker/roadmap/issues/12#issuecomment-660336629 above. As you describe I don't see any processes inside the VM using significant CPU time and no containers are running. I see you're running edge 2.3.3.0 which has the fix for the clash between osquery and hyperkit.
I'm suspicious that the diagnostics are missing one of the log files; the query to gather 1 days worth of hyperkit + other process logs timed-out after 2 minutes. Could you open Console.app and search for docker to see if something is streaming logs at a high rate? That was one of the symptoms of the clash between osquery and hyperkit and, although I believe that particular issue is fixed, perhaps there's something similar happening here.
My other suggestion is to try running sudo dtruss -p <hyperkit pid> to see if there's a large amount of I/O on a particular file descriptor and then use lsof -p <hyperkit pid> to see if it corresponds to anything interesting.
djs55
on 22 Jul 2020
@djs55 I don't see a lot of logs streaming (there are a few):
sudo dtruss -p 24990 shows lots and lots of this going on:
...
kevent(0x15, 0x0, 0x0) = 1 0
read(0x14, "\0", 0x1) = -1 35
kevent(0x15, 0x0, 0x0) = 1 0
read(0x14, "\0", 0x1) = -1 35
kevent(0x15, 0x0, 0x0) = 1 0
read(0x14, "\0", 0x1) = -1 35
kevent(0x15, 0x0, 0x0) = 1 0
read(0x14, "\0", 0x1) = -1 35
kevent(0x15, 0x0, 0x0) = 1 0
read(0x14, "\0", 0x1) = -1 35
...
I'm not sure what that means, exactly. Here is the output of lsof -p 24990, which I don't understand how to correllate:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
com.docke 24990 nate.morris cwd DIR 1,4 864 234496604 /Users/nate.morris/Library/Containers/com.docker.docker/Data
com.docke 24990 nate.morris txt REG 1,4 4350368 234495871 /Applications/Docker.app/Contents/Resources/bin/com.docker.hyperkit
com.docke 24990 nate.morris txt REG 1,4 1568368 1152921500312784940 /usr/lib/dyld
com.docke 24990 nate.morris 0r CHR 3,2 0t0 313 /dev/null
com.docke 24990 nate.morris 1 PIPE 0xa6ff74b26c2a0f64 16384 ->0x15773178e663387c
com.docke 24990 nate.morris 2 PIPE 0x934d5ad155257058 16384 ->0xbbfbce386e0d3fa7
com.docke 24990 nate.morris 3 PIPE 0xed46796e56060750 16384 ->0x332915daa4178463
com.docke 24990 nate.morris 4 PIPE 0x332915daa4178463 16384 ->0xed46796e56060750
com.docke 24990 nate.morris 5 PIPE 0x2ac8c92f3d8f5650 16384 ->0x5d671ada975fb9e8
com.docke 24990 nate.morris 6 PIPE 0x5d671ada975fb9e8 16384 ->0x2ac8c92f3d8f5650
com.docke 24990 nate.morris 7u unix 0x2c7c595212f19c25 0t0 ->0x2c7c595212f199cd
com.docke 24990 nate.morris 8u REG 1,4 63999836160 234496776 /Users/nate.morris/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw
com.docke 24990 nate.morris 9u unix 0x2c7c595212f1afad 0t0 vms/0/connect
com.docke 24990 nate.morris 10u unix 0x2c7c595212f1a7dd 0t0 vms/0/00000003.00000948
com.docke 24990 nate.morris 11u unix 0x2c7c595212f1a3f5 0t0 vms/0/00000003.000005f5
com.docke 24990 nate.morris 12 PIPE 0xdfee39cf7789db42 16384 ->0x5d8691b79a29aac3
com.docke 24990 nate.morris 13 PIPE 0x5d8691b79a29aac3 16384 ->0xdfee39cf7789db42
com.docke 24990 nate.morris 14 PIPE 0x5b75214e2989acae 16384 ->0x548a3b1ddde8de93
com.docke 24990 nate.morris 15 PIPE 0x548a3b1ddde8de93 16384 ->0x5b75214e2989acae
com.docke 24990 nate.morris 16r REG 1,4 440012800 234496082 /Applications/Docker.app/Contents/Resources/linuxkit/docker-desktop.iso
com.docke 24990 nate.morris 17r REG 1,4 139264 236277273 /Users/nate.morris/Library/Containers/com.docker.docker/Data/vms/0/config.iso
com.docke 24990 nate.morris 18r REG 1,4 279959552 234496091 /Applications/Docker.app/Contents/Resources/linuxkit/docker.iso
com.docke 24990 nate.morris 19r CHR 14,0 0t401 588 /dev/random
com.docke 24990 nate.morris 20u CHR 15,6 0t2116 582 /dev/ptmx
com.docke 24990 nate.morris 21u KQUEUE count=1, state=0x8
com.docke 24990 nate.morris 22 PIPE 0x10b8e24d06f3c9c4 16384 ->0xf64bb66c17a83b50
com.docke 24990 nate.morris 23 PIPE 0xf64bb66c17a83b50 16384 ->0x10b8e24d06f3c9c4
com.docke 24990 nate.morris 24r CHR 16,6 0t0 1367 /dev/ttys006
com.docke 24990 nate.morris 25u unix 0x2c7c59522428e64d 0t0 ->0x2c7c59522428f2cd
com.docke 24990 nate.morris 26u unix 0x2c7c59522428ca2d 0t0 ->0x2c7c59522428e32d
com.docke 24990 nate.morris 27u unix 0x2c7c59522428ee1d 0t0 ->0x2c7c59522428ce15
com.docke 24990 nate.morris 28u unix 0x2c7c59522428f45d 0t0 vms/0/connect
com.docke 24990 nate.morris 29u unix 0x2c7c5952251f838d 0t0 vms/0/connect
com.docke 24990 nate.morris 30u unix 0x2c7c5952251f9bc5 0t0 ->0x2c7c5952251f9585
com.docke 24990 nate.morris 31u unix 0x2c7c5952251f8a95 0t0 vms/0/connect
com.docke 24990 nate.morris 32u unix 0x2c7c5952251f8db5 0t0 ->0x2c7c5952251f9afd
com.docke 24990 nate.morris 33u unix 0x2c7c5952251fa45d 0t0 vms/0/connect
com.docke 24990 nate.morris 34u unix 0x2c7c5952251fa205 0t0 ->0x2c7c5952251fa525
com.docke 24990 nate.morris 35u unix 0x2c7c5952251f851d 0t0 vms/0/connect
com.docke 24990 nate.morris 36u unix 0x2c7c5952065ca83d 0t0 ->0x2c7c5952065ca51d
com.docke 24990 nate.morris 37u unix 0x2c7c5952065c9c85 0t0 vms/0/connect
com.docke 24990 nate.morris 38u unix 0x2c7c5952065cbc8d 0t0 ->0x2c7c5952065cc45d
@djs55 here is the summary output of sudo timeout 10 dtruss -p 24990 -c (stats of 10 seconds of dtruss checking the docker process) in case that helps at all:
dtrace: 344100 dynamic variable drops with non-empty dirty list
CALL COUNT
psynch_mutexdrop 1
psynch_mutexwait 1
select 7
psynch_cvsignal 9
psynch_cvwait 12
read 13615
kevent 13616
@nm777 thanks very much for the quick response. The 0x15 kevent and 0x14 read correspond to
com.docke 24990 nate.morris 20u CHR 15,6 0t2116 582 /dev/ptmx
com.docke 24990 nate.morris 21u KQUEUE count=1, state=0x8
To double-check I did a local build of hyperkit with some printfs -- the fds are opened in the same order so I get the same numbers as you.
On my healthy machine I see no kevent and only 257 read requests in ~10s.
This is very similar to the osquery clash where something generated excessive activity on the serial interface, causing high CPU usage. I think what I'll do is prepare a test build with the whole serial interface disabled -- it's only useful for low-level debug -- and share that with you tomorrow.
djs55
on 22 Jul 2020
I have Kubernetes off and I installed the latest Edge build yesterday and my CPU has been going nuts all day today: C18223FD-44DC-4ACD-B197-B660FC33917F/20200722224755
daveisfera
on 23 Jul 2020
Could you try to reproduce with a later version? Version 2.3.3.2 was released yesterday: https://desktop.docker.com/mac/edge/46784/Docker.dmg
CPU usage without any containers ~5%. Thanks a lot!
m8rge
on 23 Jul 2020
@nm777 if you have time to try it, I've made a build with the serial console disabled: https://desktop-stage.docker.com/mac/edge/46872/Docker.dmg . Unfortunately it's signed but not notarized so you may need to right-click on the app in Finder and select "Open" to run it. I'm hoping it'll be better since this version doesn't open /dev/ptmx which was implicated in the dtruss output and lsof.
djs55
on 23 Jul 2020
@djs55 After installing the version above I'm seeing CPU usage at around 2% and the suspect syscalls have pretty much gone away. Here is the dtruss output for a 10 second snapshot again:
CALL COUNT
__pthread_sigmask 3
psynch_cvclrprepost 7
writev 58
psynch_mutexdrop 75
psynch_mutexwait 81
readv 114
read 193
write 200
select 424
psynch_cvsignal 2559
psynch_cvwait 3471
I think you've isolated the source of the specific problem I am experiencing.
Is this a viable long-term fix that I could expect to see in an edge or stable version eventually or is this something that needs to be further diagnosed so a better resolution can be reached?
I'd be happy to reproduce the issue again and get you further logs or analysis if that would be helpful.
nm777
on 23 Jul 2020
@nm777 thanks for the rapid confirmation! The serial interface that I removed is intended for low-level debugging. I think I can replace it with a (safer) pair of mechanisms:
- a log of the VM console output: this is already in the experimental build
- a means of "logging in" to the VM: I'll have to experiment with this. Perhaps I can create a simple service which runs over hypervisor sockets instead of an emulated serial port.
Anyway, since this build has worked I'm happy that we've narrowed down the problem enough, so I'll put a ticket in our backlog for the remaining work. Thanks again!
djs55
on 23 Jul 2020
@djs55 as a reference installed your build, enabled K8s, no workload, i.e. only system containers running and continue to see the host burn ~40% cpu with your build.
Fyi, com.docker.supervisor is complaining about the serial interface no longer existing ;-)
Tracing syscalls with 8 vcpus configured yields:
$ sudo gtimeout 10 dtruss -p $(pgrep com.docker.hyperkit) -c
CALL COUNT
fsync 14
lseek 18
writev 18
select 38
psynch_cvclrprepost 45
psynch_mutexdrop 438
psynch_mutexwait 481
psynch_cvsignal 9019
psynch_cvwait 11724
@HarryWeppner thanks for that -- I clearly missed something in my patch to hyperkit. I'll correct the problem before we productise it :)
djs55
on 24 Jul 2020
I'm a bit confused as to which "100% cpu" issue is which ... but following the comment here: https://github.com/docker/for-mac/issues/4064#issuecomment-650101593 I'm adding details to this issue.
com.hyperkit.docker is using about 110% cpu with no containers running (kubernetes disabled). From some of the other comments I've seen, it might be relevant that I've just done a docker system prune and also deleted some data volumes.
Docker for Mac edge 2.3.3.2 (46784)
Diagnostics: 33FF6307-E436-4521-A8DF-D8660ADDA72B/20200728005541
dtruss for 10 mississippis:
CALL COUNT
psynch_cvclrprepost 21
lseek 26
writev 187
psynch_mutexdrop 456
psynch_mutexwait 486
readv 625
read 875
write 875
select 1193
psynch_cvsignal 9079
psynch_cvwait 11254
[10.53s]
Running top in the VM (with nsenter1) gives:
Mem: 722412K used, 1314328K free, 828K shrd, 18528K buff, 317500K cached
CPU: 0% usr 1% sys 0% nic 97% idle 0% io 0% irq 0% sirq
Mem: 760888K used, 1275852K free, 1492K shrd, 18724K buff, 341996K cached
CPU: 0% usr 1% sys 0% nic 98% idle 0% io 0% irq 0% sirq
Load average: 0.27 0.33 0.19 1/559 2250
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
1269 1263 root S 719m 36% 15 1% /usr/bin/lifecycle-server
485 1 root S 695m 35% 7 1% /usr/bin/vpnkit-bridge --addr connect://2/1999 guest
105 2 root IW 0 0% 14 0% [kworker/14:1-vi]
10 2 root IW 0 0% 6 0% [rcu_sched]
1657 1652 root S 1816m 90% 0 0% /usr/local/bin/dockerd --containerd /var/run/desktop-containerd/containerd.sock --pidfile /run/desktop/docker.pid
1358 1343 root S 1428m 71% 12 0% /usr/local/bin/containerd --config /etc/containerd/containerd.toml
1185 1165 root S 714m 36% 2 0% /usr/local/bin/diagnosticsd
1088 1 root S 146m 7% 3 0% /usr/bin/containerd
1405 1 root S 111m 6% 14 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id kmsg -address /run/containerd/containerd.sock
1212 1 root S 111m 6% 13 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id docker -address /run/containerd/containerd.sock
1276 1 root S 111m 6% 4 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id host-timesync-daemon -address /run/containerd/co
1556 1 root S 111m 6% 13 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id trim-after-delete -address /run/containerd/conta
1466 1 root S 111m 6% 4 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id sntpc -address /run/containerd/containerd.sock
1511 1 root S 111m 6% 14 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id socks -address /run/containerd/containerd.sock
1165 1 root S 110m 6% 13 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id diagnose -address /run/containerd/containerd.soc
1605 1 root S 110m 6% 5 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id vpnkit-forwarder -address /run/containerd/contai
1122 1 root S 110m 6% 12 0% /usr/bin/containerd-shim-runc-v2 -namespace services.linuxkit -id acpid -address /run/containerd/containerd.sock
1392 1212 root S 106m 5% 0 0% rpc.statd
2190 1358 root S 106m 5% 8 0% containerd-shim -namespace moby -workdir /var/lib/desktop-containerd/daemon/io.containerd.runtime.v1.linux/moby/07
1576 1556 root S 105m 5% 1 0% /usr/bin/trim-after-delete -- /sbin/fstrim /var/lib/docker
476 1 root S 104m 5% 6 0% /usr/bin/memlogd -fd-log 3 -fd-query 4 -max-lines 5000 -max-line-len 1024
1437 1405 root S 102m 5% 5 0% /usr/bin/kmsg
1652 1269 root S 101m 5% 15 0% /usr/bin/logwrite -n dockerd /usr/local/bin/dockerd --containerd /var/run/desktop-containerd/containerd.sock --pid
1343 1269 root S 101m 5% 0 0% /usr/bin/logwrite -n containerd /usr/local/bin/containerd --config /etc/containerd/containerd.toml
1263 1262 root S 101m 5% 12 0% /usr/bin/logwrite -n lifecycle-server /usr/bin/lifecycle-server
1305 1276 root S 101m 5% 9 0% /usr/bin/host-timesync-daemon -port 0xf3a4
1333 1332 root S 15816 1% 3 0% /usr/bin/transfused
1625 1605 root S 11096 1% 3 0% /vpnkit-forwarder -data-connect /run/host-services/vpnkit-data.sock
1335 1212 100 S 10616 1% 0 0% rpcbind
462 1 root S 1600 0% 13 0% {rungetty.sh} /bin/sh /usr/bin/rungetty.sh
465 1 root S 1600 0% 3 0% {rungetty.sh} /bin/sh /usr/bin/rungetty.sh
2214 2190 root S 1596 0% 11 0% /bin/sh
471 466 root S 1596 0% 15 0% -sh
470 464 root S 1596 0% 7 0% -sh
1332 1212 root S 1576 0% 6 0% {transfused.sh} /bin/sh /usr/bin/transfused.sh
1262 1244 root S 1572 0% 11 0% {entrypoint.sh} /bin/sh /usr/bin/entrypoint.sh
JonyEpsilon
on 28 Jul 2020
Docker version: Docker for Mac edge 2.3.3.2 (46784)
Diagnostic ID: 89AF1A5C-6D7D-4E0C-8DB6-ADCEF911F562/20200728104708
More than 100% CPU utilization, my MacBook is no less than a hot iron bar.
navneet0693
on 28 Jul 2020
Hi -- a quick progress update on the Mac CPU issue: It seems to be a mixture of several bugs including
- excessively large queues of events in the filesharing implementation -- there is a proposed fix for this but it's not in any current release build
- a clash with
osqueryover thehyperkitserial console: this is fixed in Edge but not in Stable - a further problem with the
hyperkitserial console: there is a proposed fix for this but it's not in any current release build
(and possibly more, since the symptoms are all very similar it means they're hard to tell apart)
There is a development build with all the current known fixes (for 1, 2 and 3): https://desktop-stage.docker.com/mac/edge/47050/Docker.dmg (Edited to make this a notarized build). If you have a chance to try it, please do and let me know how it goes. Unfortunately the build is signed but not notarized so you will need to open it in finder, right click and click on "Open" to bypass the notarization check. I'm very interested to hear both about any bugs in this build and about any remaining CPU issues. Thanks!
djs55
on 30 Jul 2020
@djs55 thanks for the update! Our corporate policy won't let us run software which is not notarized. Any possibly to get a build we could test with a number of our folks having performance issues?
chezsmithy
on 31 Jul 2020
@chezsmithy no problem, I've notarized the build and updated the comment above. This one should be notarized https://desktop-stage.docker.com/mac/edge/47050/Docker.dmg
djs55
on 31 Jul 2020
@djs55 I've installed the 47050 build and did a complete reset. Without kubernetes I observe a cpu usage of approx. 4% and with kubernetes enabled it's around 43% (both numbers are on a clean install, no containers running other than the system ones).
dvic
on 31 Jul 2020
Thanks for the report, @dvic. That's actually not too bad.
On Kubernetes, we're very limited what we can do. We may be able to make some configuration improvements to reduce the CPU load a bit, but most of the problems are upstream and other Kubernetes desktop distributions have exactly the same issues.
stephen-turner
on 31 Jul 2020
@djs55 @stephen-turner I have installed it too and it looks good. Idle without a container running only 1-2% cpu usage (Kubernets deactivated). With one container running it jumps between high cpu usage for 1-2 seconda and then back to one digit cpu usage for another few seconds instead of >100% all the time like in previous builds.
chnbz
on 31 Jul 2020
First tests of the build in https://github.com/docker/roadmap/issues/12#issuecomment-666279931 are positive, com.docker.hyperkit is still spiking but not continuously high.
vredeling
on 31 Jul 2020
@djs55, I had the issue with the serial console events above and this recent build still has low CPU usage for me (I haven't actually run any containers yet). Thanks for your work on these issues!
nm777
on 3 Aug 2020
Hi everyone. We'd love you to try out our latest Edge release, 2.3.5.0. This has all our best fixes for CPU improvements. You can get it at https://desktop.docker.com/mac/edge/47376/Docker.dmg.
The largest change is that (by default) it uses gRPC-FUSE instead of osxfs. This brings a big improvement in file sharing speed as well as CPU usage. We think that the majority of the CPU problems in previous versions are osxfs related.
For CPU load when using Kubernetes, we have made some improvements by supplying some different arguments to Kubernetes. There are still some problems that can only be fixed upstream, but it is improved in this release.
There are a few other unrelated fixes too (and actually, one last one we're still working on).
Assuming no major bugs, these fixes will make it into the next Stable release. So for anyone who can try the Edge release, we would love you to do so and give us some feedback. Are you seeing CPU improvements? Any remaining issues?
Thank you.
stephen-turner
on 21 Aug 2020
Right after startup Docker for Mac is using constantly ~200%, while com.docker.hyperkit is consuming ~ 2%. No active containers. After quitting and restarting a few times is back to ~0-1%.
Sample of Docker
Sampling process 92219 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling Docker (pid 92219) every 1 millisecond
Process: Docker [92219]
Path: /Applications/Docker.app/Contents/MacOS/Docker
Load Address: 0x103981000
Identifier: com.docker.docker
Version: 2.0.0.3 (31259)
Code Type: X86-64
Parent Process: ??? [1]
Date/Time: 2020-08-25 10:55:12.383 +0200
Launch Time: 2020-08-25 10:50:16.707 +0200
OS Version: Mac OS X 10.15.6 (19G73)
Report Version: 7
Analysis Tool: /usr/bin/sample
Physical footprint: 15.3M
Physical footprint (peak): 15.5M
----
Call graph:
2709 Thread_1609588 DispatchQueue_1: com.apple.main-thread (serial)
+ 2709 start (in libdyld.dylib) + 1 [0x7fff70276cc9]
+ 2709 main (in Docker) + 9 [0x103984179]
+ 2709 NSApplicationMain (in AppKit) + 777 [0x7fff3343e396]
+ 2709 -[NSApplication run] (in AppKit) + 658 [0x7fff3346c58e]
+ 2709 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] (in AppKit) + 1352 [0x7fff3347a880]
+ 2709 _DPSNextEvent (in AppKit) + 883 [0x7fff3347c039]
+ 2709 _BlockUntilNextEventMatchingListInModeWithFilter (in HIToolbox) + 64 [0x7fff34e36579]
+ 2709 ReceiveNextEventCommon (in HIToolbox) + 584 [0x7fff34e367d5]
+ 2709 RunCurrentEventLoopInMode (in HIToolbox) + 292 [0x7fff34e36abd]
+ 2709 CFRunLoopRunSpecific (in CoreFoundation) + 462 [0x7fff36209e3e]
+ 2709 __CFRunLoopRun (in CoreFoundation) + 1319 [0x7fff3620a9c2]
+ 2709 __CFRunLoopServiceMachPort (in CoreFoundation) + 247 [0x7fff3620bef5]
+ 2709 mach_msg (in libsystem_kernel.dylib) + 60 [0x7fff703b8170]
+ 2709 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x7fff703b7dfa]
2709 Thread_1609624 DispatchQueue_6: com.apple.root.background-qos (concurrent)
+ 2709 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
+ 2709 _pthread_wqthread (in libsystem_pthread.dylib) + 220 [0x7fff704779f7]
+ 2709 _dispatch_worker_thread2 (in libdispatch.dylib) + 92 [0x7fff7022c097]
+ 2709 _dispatch_root_queue_drain (in libdispatch.dylib) + 663 [0x7fff7022baa8]
+ 2709 _dispatch_client_callout (in libdispatch.dylib) + 8 [0x7fff7021d658]
+ 2709 _dispatch_block_async_invoke2 (in libdispatch.dylib) + 83 [0x7fff702292b9]
+ 2709 thunk for @escaping @callee_guaranteed () -> () (in Docker) + 32 [0x103998af0]
+ 2709 partial apply for specialized closure #1 in static AsyncBlock.async<A>(after:block:queue:) (in Docker) + 21 [0x1039eeb55]
+ 2709 specialized closure #1 in static AsyncBlock.async<A>(after:block:queue:) (in Docker) + 15 [0x1039989ef]
+ 2709 partial apply for thunk for @escaping @callee_guaranteed () -> () (in Docker) + 17 [0x1039eeb31]
+ 2709 thunk for @escaping @callee_guaranteed () -> () (in Docker) + 12 [0x103983c8c]
+ 2709 partial apply for closure #1 in BackendImpl.listen() (in Docker) + 12 [0x1039eeafc]
+ 2709 closure #1 in BackendImpl.listen() (in Docker) + 84 [0x1039ed364]
+ 2709 specialized BackendDialer.listen(_:) (in Docker) + 3202 [0x103a3d8e2]
+ 2709 __accept (in libsystem_kernel.dylib) + 10 [0x7fff703be3be]
2709 Thread_1609645: com.apple.NSEventThread
+ 2709 thread_start (in libsystem_pthread.dylib) + 15 [0x7fff70476b8b]
+ 2709 _pthread_start (in libsystem_pthread.dylib) + 148 [0x7fff7047b109]
+ 2709 _NSEventThread (in AppKit) + 132 [0x7fff3361d954]
+ 2709 CFRunLoopRunSpecific (in CoreFoundation) + 462 [0x7fff36209e3e]
+ 2709 __CFRunLoopRun (in CoreFoundation) + 1319 [0x7fff3620a9c2]
+ 2709 __CFRunLoopServiceMachPort (in CoreFoundation) + 247 [0x7fff3620bef5]
+ 2709 mach_msg (in libsystem_kernel.dylib) + 60 [0x7fff703b8170]
+ 2709 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x7fff703b7dfa]
2709 Thread_1614992
+ 2709 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
+ 2709 _pthread_wqthread (in libsystem_pthread.dylib) + 390 [0x7fff70477aa1]
+ 2709 __workq_kernreturn (in libsystem_kernel.dylib) + 10 [0x7fff703b94ce]
2342 Thread_1613132
+ 2273 start_wqthread (in libsystem_pthread.dylib) + 0,2,... [0x7fff70476b68,0x7fff70476b6a,...]
+ 54 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
+ ! 52 _pthread_wqthread (in libsystem_pthread.dylib) + 290 [0x7fff70477a3d]
+ ! : 42 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 293 [0x7fff7022cada]
+ ! : | 32 _dispatch_event_loop_merge (in libdispatch.dylib) + 119 [0x7fff70238634]
+ ! : | + 15 _dispatch_lane_push (in libdispatch.dylib) + 59,86,... [0x7fff70225bd4,0x7fff70225bef,...]
+ ! : | + 11 _dispatch_kevent_merge (in libdispatch.dylib) + 51,19,... [0x7fff7023a56b,0x7fff7023a54b,...]
+ ! : | + 3 _dispatch_lane_wakeup (in libdispatch.dylib) + 11,17 [0x7fff70225a3d,0x7fff70225a43]
+ ! : | + 1 _dispatch_event_loop_poke (in libdispatch.dylib) + 702 [0x7fff70238121]
+ ! : | + 1 _dispatch_kevent_drain (in libdispatch.dylib) + 164 [0x7fff7023874a]
+ ! : | + 1 _dispatch_source_wakeup (in libdispatch.dylib) + 171 [0x7fff7022f9e3]
+ ! : | 6 _dispatch_queue_wakeup (in libdispatch.dylib) + 141,5,... [0x7fff702254e0,0x7fff70225458,...]
+ ! : | 4 _dispatch_event_loop_merge (in libdispatch.dylib) + 0,30,... [0x7fff702385bd,0x7fff702385db,...]
+ ! : 10 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 194,8,... [0x7fff7022ca77,0x7fff7022c9bd,...]
+ ! 1 _pthread_wqthread (in libsystem_pthread.dylib) + 390 [0x7fff70477aa1]
+ ! : 1 __workq_kernreturn (in libsystem_kernel.dylib) + 0 [0x7fff703b94c4]
+ ! 1 _pthread_wqthread (in libsystem_pthread.dylib) + 241 [0x7fff70477a0c]
+ 15 _dispatch_queue_wakeup (in libdispatch.dylib) + 355,185,... [0x7fff702255b6,0x7fff7022550c,...]
2280 Thread_1610153
+ 2143 start_wqthread (in libsystem_pthread.dylib) + 0,2,... [0x7fff70476b68,0x7fff70476b6a,...]
+ 116 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
+ ! 106 _pthread_wqthread (in libsystem_pthread.dylib) + 290 [0x7fff70477a3d]
+ ! : 77 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 293 [0x7fff7022cada]
+ ! : | 53 _dispatch_event_loop_merge (in libdispatch.dylib) + 119 [0x7fff70238634]
+ ! : | + 19 _dispatch_kevent_merge (in libdispatch.dylib) + 51,19,... [0x7fff7023a56b,0x7fff7023a54b,...]
+ ! : | + 17 _dispatch_lane_push (in libdispatch.dylib) + 86,59,... [0x7fff70225bef,0x7fff70225bd4,...]
+ ! : | + 7 _dispatch_source_merge_evt (in libdispatch.dylib) + 89,6,... [0x7fff7022fdd3,0x7fff7022fd80,...]
+ ! : | + 5 _dispatch_event_loop_poke (in libdispatch.dylib) + 0,1,... [0x7fff70237e63,0x7fff70237e64,...]
+ ! : | + 4 _dispatch_source_wakeup (in libdispatch.dylib) + 4,0,... [0x7fff7022f93c,0x7fff7022f938,...]
+ ! : | + 1 _dispatch_kevent_drain (in libdispatch.dylib) + 4 [0x7fff702386aa]
+ ! : | 12 _dispatch_event_loop_merge (in libdispatch.dylib) + 30,0,... [0x7fff702385db,0x7fff702385bd,...]
+ ! : | 5 _dispatch_event_loop_merge (in libdispatch.dylib) + 99 [0x7fff70238620]
+ ! : | + 5 _platform_memmove$VARIANT$Haswell (in libsystem_platform.dylib) + 111,0,... [0x7fff7046c96f,0x7fff7046c900,...]
+ ! : | 3 _dispatch_queue_wakeup (in libdispatch.dylib) + 5,103,... [0x7fff70225458,0x7fff702254ba,...]
+ ! : | 2 DYLD-STUB$$memcpy (in libdispatch.dylib) + 0 [0x7fff7024d66a]
+ ! : | 1 ___chkstk_darwin (in libsystem_pthread.dylib) + 17 [0x7fff70476ba1]
+ ! : | 1 __chkstk_darwin (in libdispatch.dylib) + 23 [0x7fff70236007]
+ ! : | 1 ___chkstk_darwin (in libsystem_pthread.dylib) + 45 [0x7fff70476bbd]
+ ! : 29 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 194,0,... [0x7fff7022ca77,0x7fff7022c9b5,...]
+ ! 7 _pthread_wqthread (in libsystem_pthread.dylib) + 0,10,... [0x7fff7047791b,0x7fff70477925,...]
+ ! 3 _pthread_wqthread (in libsystem_pthread.dylib) + 390 [0x7fff70477aa1]
+ ! 3 __workq_kernreturn (in libsystem_kernel.dylib) + 0,10 [0x7fff703b94c4,0x7fff703b94ce]
+ 21 _dispatch_queue_wakeup (in libdispatch.dylib) + 355,728,... [0x7fff702255b6,0x7fff7022572b,...]
342 Thread_1610153 DispatchQueue_381: com.apple.NSFileHandle.1 (serial)
+ 342 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
+ 342 _pthread_wqthread (in libsystem_pthread.dylib) + 290 [0x7fff70477a3d]
+ 342 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 596 [0x7fff7022cc09]
+ 326 _dispatch_lane_invoke (in libdispatch.dylib) + 363 [0x7fff702235d6]
+ ! 305 _dispatch_lane_serial_drain (in libdispatch.dylib) + 263 [0x7fff70222af6]
+ ! : 200 _dispatch_source_invoke (in libdispatch.dylib) + 2084 [0x7fff7022f4be]
+ ! : | 191 _dispatch_continuation_pop (in libdispatch.dylib) + 414 [0x7fff7021f818]
+ ! : | + 190 _dispatch_client_callout (in libdispatch.dylib) + 8 [0x7fff7021d658]
+ ! : | + ! 84 __46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) + 148 [0x7fff389e536a]
+ ! : | + ! : 40 _pthread_mutex_firstfit_unlock_slow (in libsystem_pthread.dylib) + 202,174,... [0x7fff70476ade,0x7fff70476ac2,...]
+ ! : | + ! : 30 CFRunLoopSourceSignal (in CoreFoundation) + 52 [0x7fff362056d4]
+ ! : | + ! : | 24 _pthread_mutex_firstfit_lock_slow (in libsystem_pthread.dylib) + 173,181,... [0x7fff70476906,0x7fff7047690e,...]
+ ! : | + ! : | 4 pthread_mutex_lock (in libsystem_pthread.dylib) + 0,7,... [0x7fff704765ad,0x7fff704765b4,...]
+ ! : | + ! : | 2 _pthread_mutex_lock_init_slow (in libsystem_pthread.dylib) + 6,65 [0x7fff7047663c,0x7fff70476677]
+ ! : | + ! : 9 CFRunLoopSourceSignal (in CoreFoundation) + 0,6,... [0x7fff362056a0,0x7fff362056a6,...]
+ ! : | + ! : 4 _pthread_mutex_unlock_init_slow (in libsystem_pthread.dylib) + 63,42 [0x7fff70476a05,0x7fff704769f0]
+ ! : | + ! : 1 DYLD-STUB$$pthread_mutex_lock (in CoreFoundation) + 0 [0x7fff3634261a]
+ ! : | + ! 30 CFRunLoopWakeUp (in CoreFoundation) + 101 [0x7fff361f0b31]
+ ! : | + ! : 28 _pthread_mutex_firstfit_lock_slow (in libsystem_pthread.dylib) + 181,173,... [0x7fff7047690e,0x7fff70476906,...]
+ ! : | + ! : 2 pthread_mutex_lock (in libsystem_pthread.dylib) + 120 [0x7fff70476625]
+ ! : | + ! 24 _pthread_mutex_firstfit_unlock_slow (in libsystem_pthread.dylib) + 174,202,... [0x7fff70476ac2,0x7fff70476ade,...]
+ ! : | + ! 16 __46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) + 44 [0x7fff389e5302]
+ ! : | + ! : 16 os_unfair_lock_lock (in libsystem_platform.dylib) + 14,8 [0x7fff7046cef8,0x7fff7046cef2]
+ ! : | + ! 12 __46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) + 0,1,... [0x7fff389e52d6,0x7fff389e52d7,...]
+ ! : | + ! 11 CFRunLoopWakeUp (in CoreFoundation) + 89,0,... [0x7fff361f0b25,0x7fff361f0acc,...]
+ ! : | + ! 10 __46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) + 69 [0x7fff389e531b]
+ ! : | + ! : 10 os_unfair_lock_unlock (in libsystem_platform.dylib) + 12 [0x7fff7046c7c3]
+ ! : | + ! 2 _pthread_mutex_unlock_init_slow (in libsystem_pthread.dylib) + 5,15 [0x7fff704769cb,0x7fff704769d5]
+ ! : | + ! 1 DYLD-STUB$$pthread_mutex_lock (in CoreFoundation) + 0 [0x7fff3634261a]
+ ! : | + 1 _dispatch_client_callout (in libdispatch.dylib) + 12 [0x7fff7021d65c]
+ ! : | 9 _dispatch_continuation_pop (in libdispatch.dylib) + 0,1,... [0x7fff7021f67a,0x7fff7021f67b,...]
+ ! : 78 _dispatch_source_invoke (in libdispatch.dylib) + 1389,2964,... [0x7fff7022f207,0x7fff7022f82e,...]
+ ! : 18 _dispatch_source_invoke (in libdispatch.dylib) + 1539 [0x7fff7022f29d]
+ ! : | 16 _dispatch_kq_unote_update (in libdispatch.dylib) + 543,798,... [0x7fff70237bc0,0x7fff70237cbf,...]
+ ! : | 2 _dispatch_unote_resume_direct (in libdispatch.dylib) + 0 [0x7fff70237d8e]
+ ! : 9 _dispatch_source_invoke (in libdispatch.dylib) + 3171 [0x7fff7022f8fd]
+ ! : 9 _os_object_release_internal_n (in libdispatch.dylib) + 19 [0x7fff7021c9fa]
+ ! 21 _dispatch_lane_serial_drain (in libdispatch.dylib) + 211,1306,... [0x7fff70222ac2,0x7fff70222f09,...]
+ 14 _dispatch_lane_invoke (in libdispatch.dylib) + 479 [0x7fff7022364a]
+ ! 13 _dispatch_last_resort_autorelease_pool_pop (in libdispatch.dylib) + 27 [0x7fff7021d641]
+ ! : 10 objc_autoreleasePoolPop (in libobjc.A.dylib) + 115,0,... [0x7fff6f0c3d7e,0x7fff6f0c3d0b,...]
+ ! : 3 objc_autoreleasePoolPop (in libobjc.A.dylib) + 175 [0x7fff6f0c3dba]
+ ! : 3 AutoreleasePoolPage::releaseUntil(objc_object**) (in libobjc.A.dylib) + 13,50,... [0x7fff6f0defdb,0x7fff6f0df000,...]
+ ! 1 _dispatch_last_resort_autorelease_pool_pop (in libdispatch.dylib) + 39 [0x7fff7021d64d]
+ 2 _dispatch_lane_invoke (in libdispatch.dylib) + 458,471 [0x7fff70223635,0x7fff70223642]
303 Thread_1613132 DispatchQueue_1035: com.apple.NSFileHandle.1 (serial)
+ 303 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
+ 303 _pthread_wqthread (in libsystem_pthread.dylib) + 290 [0x7fff70477a3d]
+ 303 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 596 [0x7fff7022cc09]
+ 291 _dispatch_lane_invoke (in libdispatch.dylib) + 363 [0x7fff702235d6]
+ ! 268 _dispatch_lane_serial_drain (in libdispatch.dylib) + 263 [0x7fff70222af6]
+ ! : 183 _dispatch_source_invoke (in libdispatch.dylib) + 2084 [0x7fff7022f4be]
+ ! : | 165 _dispatch_continuation_pop (in libdispatch.dylib) + 414 [0x7fff7021f818]
+ ! : | + 163 _dispatch_client_callout (in libdispatch.dylib) + 8 [0x7fff7021d658]
+ ! : | + ! 63 __46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) + 148 [0x7fff389e536a]
+ ! : | + ! : 30 _pthread_mutex_firstfit_unlock_slow (in libsystem_pthread.dylib) + 174,202,... [0x7fff70476ac2,0x7fff70476ade,...]
+ ! : | + ! : 24 CFRunLoopSourceSignal (in CoreFoundation) + 52 [0x7fff362056d4]
+ ! : | + ! : | 22 _pthread_mutex_firstfit_lock_slow (in libsystem_pthread.dylib) + 181,1,... [0x7fff7047690e,0x7fff7047685a,...]
+ ! : | + ! : | 1 _pthread_mutex_lock_init_slow (in libsystem_pthread.dylib) + 44 [0x7fff70476662]
+ ! : | + ! : | 1 pthread_mutex_lock (in libsystem_pthread.dylib) + 0 [0x7fff704765ad]
+ ! : | + ! : 5 _pthread_mutex_unlock_init_slow (in libsystem_pthread.dylib) + 15,0,... [0x7fff704769d5,0x7fff704769c6,...]
+ ! : | + ! : 2 CFRunLoopSourceSignal (in CoreFoundation) + 0,1 [0x7fff362056a0,0x7fff362056a1]
+ ! : | + ! : 1 DYLD-STUB$$pthread_mutex_lock (in CoreFoundation) + 0 [0x7fff3634261a]
+ ! : | + ! : 1 pthread_mutex_unlock (in libsystem_pthread.dylib) + 0 [0x7fff70476968]
+ ! : | + ! 25 CFRunLoopWakeUp (in CoreFoundation) + 101 [0x7fff361f0b31]
+ ! : | + ! : 17 _pthread_mutex_firstfit_lock_slow (in libsystem_pthread.dylib) + 181,173,... [0x7fff7047690e,0x7fff70476906,...]
+ ! : | + ! : 5 pthread_mutex_lock (in libsystem_pthread.dylib) + 7,0,... [0x7fff704765b4,0x7fff704765ad,...]
+ ! : | + ! : 3 _pthread_mutex_lock_init_slow (in libsystem_pthread.dylib) + 6,16,... [0x7fff7047663c,0x7fff70476646,...]
+ ! : | + ! 18 _pthread_mutex_firstfit_unlock_slow (in libsystem_pthread.dylib) + 174,202,... [0x7fff70476ac2,0x7fff70476ade,...]
+ ! : | + ! 16 __46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) + 44 [0x7fff389e5302]
+ ! : | + ! : 16 os_unfair_lock_lock (in libsystem_platform.dylib) + 14,0 [0x7fff7046cef8,0x7fff7046ceea]
+ ! : | + ! 15 __46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) + 69 [0x7fff389e531b]
+ ! : | + ! : 15 os_unfair_lock_unlock (in libsystem_platform.dylib) + 12,0 [0x7fff7046c7c3,0x7fff7046c7b7]
+ ! : | + ! 9 __46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) + 0,4,... [0x7fff389e52d6,0x7fff389e52da,...]
+ ! : | + ! 6 CFRunLoopWakeUp (in CoreFoundation) + 56,0,... [0x7fff361f0b04,0x7fff361f0acc,...]
+ ! : | + ! 5 _pthread_mutex_unlock_init_slow (in libsystem_pthread.dylib) + 0,15,... [0x7fff704769c6,0x7fff704769d5,...]
+ ! : | + ! 3 DYLD-STUB$$os_unfair_lock_lock (in Foundation) + 0 [0x7fff38b4db76]
+ ! : | + ! 2 pthread_mutex_unlock (in libsystem_pthread.dylib) + 0 [0x7fff70476968]
+ ! : | + ! 1 DYLD-STUB$$pthread_mutex_lock (in CoreFoundation) + 0 [0x7fff3634261a]
+ ! : | + 1 DYLD-STUB$$pthread_mutex_unlock (in CoreFoundation) + 0 [0x7fff36342620]
+ ! : | + 1 _dispatch_client_callout (in libdispatch.dylib) + 12 [0x7fff7021d65c]
+ ! : | 18 _dispatch_continuation_pop (in libdispatch.dylib) + 476,59,... [0x7fff7021f856,0x7fff7021f6b5,...]
+ ! : 53 _dispatch_source_invoke (in libdispatch.dylib) + 953,1389,... [0x7fff7022f053,0x7fff7022f207,...]
+ ! : 21 _dispatch_source_invoke (in libdispatch.dylib) + 3171 [0x7fff7022f8fd]
+ ! : | 21 _os_object_release_internal_n (in libdispatch.dylib) + 19,0,... [0x7fff7021c9fa,0x7fff7021c9e7,...]
+ ! : 11 _dispatch_source_invoke (in libdispatch.dylib) + 1539 [0x7fff7022f29d]
+ ! : 10 _dispatch_kq_unote_update (in libdispatch.dylib) + 467,4,... [0x7fff70237b74,0x7fff702379a5,...]
+ ! : 1 _dispatch_unote_resume_direct (in libdispatch.dylib) + 3 [0x7fff70237d91]
+ ! 23 _dispatch_lane_serial_drain (in libdispatch.dylib) + 211,202,... [0x7fff70222ac2,0x7fff70222ab9,...]
+ 11 _dispatch_lane_invoke (in libdispatch.dylib) + 479 [0x7fff7022364a]
+ ! 11 _dispatch_last_resort_autorelease_pool_pop (in libdispatch.dylib) + 27 [0x7fff7021d641]
+ ! 6 objc_autoreleasePoolPop (in libobjc.A.dylib) + 175 [0x7fff6f0c3dba]
+ ! : 6 AutoreleasePoolPage::releaseUntil(objc_object**) (in libobjc.A.dylib) + 0,6,... [0x7fff6f0defce,0x7fff6f0defd4,...]
+ ! 5 objc_autoreleasePoolPop (in libobjc.A.dylib) + 5,115,... [0x7fff6f0c3d10,0x7fff6f0c3d7e,...]
+ 1 _dispatch_lane_invoke (in libdispatch.dylib) + 483 [0x7fff7022364e]
87 Thread_1610153 DispatchQueue_11: com.apple.root.default-qos.overcommit (concurrent)
+ 72 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
+ ! 72 _pthread_wqthread (in libsystem_pthread.dylib) + 290 [0x7fff70477a3d]
+ ! 55 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 596 [0x7fff7022cc09]
+ ! : 31 _dispatch_lane_invoke (in libdispatch.dylib) + 617,0,... [0x7fff702236d4,0x7fff7022346b,...]
+ ! : 12 _dispatch_lane_invoke (in libdispatch.dylib) + 321 [0x7fff702235ac]
+ ! : | 6 _dispatch_last_resort_autorelease_pool_push (in libdispatch.dylib) + 23 [0x7fff7021d61b]
+ ! : | + 6 objc_autoreleasePoolPush (in libobjc.A.dylib) + 4,0,... [0x7fff6f0c3ca9,0x7fff6f0c3ca5,...]
+ ! : | 6 _dispatch_last_resort_autorelease_pool_push (in libdispatch.dylib) + 0,15,... [0x7fff7021d604,0x7fff7021d613,...]
+ ! : 9 _dispatch_lane_invoke (in libdispatch.dylib) + 1321 [0x7fff70223994]
+ ! : | 9 _os_object_release_internal_n (in libdispatch.dylib) + 19,23 [0x7fff7021c9fa,0x7fff7021c9fe]
+ ! : 3 _dispatch_lane_invoke (in libdispatch.dylib) + 363 [0x7fff702235d6]
+ ! : 3 _dispatch_lane_serial_drain (in libdispatch.dylib) + 17,46,... [0x7fff70222a00,0x7fff70222a1d,...]
+ ! 13 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 532,358,... [0x7fff7022cbc9,0x7fff7022cb1b,...]
+ ! 2 _dispatch_event_loop_leave_deferred (in libdispatch.dylib) + 53,70 [0x7fff70238a78,0x7fff70238a89]
+ ! 2 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 1838 [0x7fff7022d0e3]
+ ! 2 _dispatch_event_loop_leave_deferred (in libdispatch.dylib) + 39 [0x7fff70238a6a]
+ 15 _dispatch_event_loop_leave_deferred (in libdispatch.dylib) + 98,111,... [0x7fff70238aa5,0x7fff70238ab2,...]
64 Thread_1613132 DispatchQueue_11: com.apple.root.default-qos.overcommit (concurrent)
59 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
! 59 _pthread_wqthread (in libsystem_pthread.dylib) + 290 [0x7fff70477a3d]
! 43 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 596 [0x7fff7022cc09]
! : 27 _dispatch_lane_invoke (in libdispatch.dylib) + 617,1334,... [0x7fff702236d4,0x7fff702239a1,...]
! : 9 _dispatch_lane_invoke (in libdispatch.dylib) + 1321 [0x7fff70223994]
! : | 9 _os_object_release_internal_n (in libdispatch.dylib) + 19,21 [0x7fff7021c9fa,0x7fff7021c9fc]
! : 4 _dispatch_lane_invoke (in libdispatch.dylib) + 363 [0x7fff702235d6]
! : | 4 _dispatch_lane_serial_drain (in libdispatch.dylib) + 1233,1,... [0x7fff70222ec0,0x7fff702229f0,...]
! : 3 _dispatch_lane_invoke (in libdispatch.dylib) + 321 [0x7fff702235ac]
! : 2 _dispatch_last_resort_autorelease_pool_push (in libdispatch.dylib) + 23 [0x7fff7021d61b]
! : + 2 objc_autoreleasePoolPush (in libobjc.A.dylib) + 0,42 [0x7fff6f0c3ca5,0x7fff6f0c3ccf]
! : 1 _dispatch_last_resort_autorelease_pool_push (in libdispatch.dylib) + 23 [0x7fff7021d61b]
! 16 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 532,407,... [0x7fff7022cbc9,0x7fff7022cb4c,...]
5 _dispatch_event_loop_leave_deferred (in libdispatch.dylib) + 95,111,... [0x7fff70238aa2,0x7fff70238ab2,...]
Total number in stack (recursive counted multiple, when >=5):
8 start_wqthread (in libsystem_pthread.dylib) + 15 [0x7fff70476b77]
6 _pthread_wqthread (in libsystem_pthread.dylib) + 290 [0x7fff70477a3d]
Sort by top of stack, same collapsed (when >= 5):
mach_msg_trap (in libsystem_kernel.dylib) 5418
start_wqthread (in libsystem_pthread.dylib) 4416
__workq_kernreturn (in libsystem_kernel.dylib) 2713
__accept (in libsystem_kernel.dylib) 2709
_dispatch_source_invoke (in libdispatch.dylib) 131
_pthread_mutex_firstfit_unlock_slow (in libsystem_pthread.dylib) 112
_pthread_mutex_firstfit_lock_slow (in libsystem_pthread.dylib) 91
_dispatch_workloop_worker_thread (in libdispatch.dylib) 68
_dispatch_lane_invoke (in libdispatch.dylib) 61
_dispatch_lane_serial_drain (in libdispatch.dylib) 51
_os_object_release_internal_n (in libdispatch.dylib) 48
_dispatch_queue_wakeup (in libdispatch.dylib) 45
_dispatch_lane_push (in libdispatch.dylib) 32
os_unfair_lock_lock (in libsystem_platform.dylib) 32
_dispatch_kevent_merge (in libdispatch.dylib) 30
_dispatch_continuation_pop (in libdispatch.dylib) 27
_dispatch_kq_unote_update (in libdispatch.dylib) 26
os_unfair_lock_unlock (in libsystem_platform.dylib) 25
_dispatch_event_loop_leave_deferred (in libdispatch.dylib) 24
__46-[NSConcreteFileHandle performActivity:modes:]_block_invoke.192 (in Foundation) 21
CFRunLoopWakeUp (in CoreFoundation) 17
_dispatch_event_loop_merge (in libdispatch.dylib) 16
_pthread_mutex_unlock_init_slow (in libsystem_pthread.dylib) 16
objc_autoreleasePoolPop (in libobjc.A.dylib) 15
pthread_mutex_lock (in libsystem_pthread.dylib) 12
CFRunLoopSourceSignal (in CoreFoundation) 11
AutoreleasePoolPage::releaseUntil(objc_object**) (in libobjc.A.dylib) 9
_pthread_wqthread (in libsystem_pthread.dylib) 8
objc_autoreleasePoolPush (in libobjc.A.dylib) 8
_dispatch_last_resort_autorelease_pool_push (in libdispatch.dylib) 7
_dispatch_source_merge_evt (in libdispatch.dylib) 7
_dispatch_event_loop_poke (in libdispatch.dylib) 6
_pthread_mutex_lock_init_slow (in libsystem_pthread.dylib) 6
_dispatch_source_wakeup (in libdispatch.dylib) 5
_platform_memmove$VARIANT$Haswell (in libsystem_platform.dylib) 5
Binary Images:
0x103981000 - 0x103ab8ff7 +com.docker.docker (2.0.0.3 - 31259) <A314B228-6FF0-32BB-B225-AE2701154C87> /Applications/Docker.app/Contents/MacOS/Docker
0x103ca4000 - 0x103cd6ff7 +ZIPFoundation (1.0 - 0.9.6) <F5BF7519-F77A-3E30-A93B-26002EA8C0F1> /Applications/Docker.app/Contents/Frameworks/ZIPFoundation.framework/Versions/A/ZIPFoundation
0x103d2b000 - 0x103d6bff7 +com.bugsnag.Bugsnag (1.0 - 1) <C2A5FD78-363C-3F20-841E-F7B2A64FF585> /Applications/Docker.app/Contents/Frameworks/Bugsnag.framework/Versions/A/Bugsnag
0x103dde000 - 0x103dedfff +com.antitypical.Result (3.2.4 - 1) <ED51541C-E74E-313C-B681-1AD142AE799D> /Applications/Docker.app/Contents/Frameworks/Result.framework/Versions/A/Result
0x103e12000 - 0x103e3dfff +com.kishikawakatsumi.KeychainAccess (3.1.0 - 1) <635EC4A1-1378-3905-B60C-AEC73F6BA483> /Applications/Docker.app/Contents/Frameworks/KeychainAccess.framework/Versions/A/KeychainAccess
0x103e7c000 - 0x103ebafff +com.cocoawithlove.CwlUtils-macOS (1.0 - ???) <5D3593AC-A68A-325C-B8CD-A210A11C62A8> /Applications/Docker.app/Contents/Frameworks/CwlUtils.framework/Versions/A/CwlUtils
0x103f42000 - 0x103f49ff7 +Eonil.EonilFileSystemEvents (1.0.0 - 1) <3E340F16-E192-3F3A-9A12-B512135413D8> /Applications/Docker.app/Contents/Frameworks/EonilFileSystemEvents.framework/Versions/A/EonilFileSystemEvents
0x103f65000 - 0x103fafff7 +org.sparkle-project.Sparkle (1.20.0 - 1.20.0) <3BE6881C-7AE6-36FD-B8D5-916E4852CD9E> /Applications/Docker.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
0x104003000 - 0x104017ff7 +libswiftAppKit.dylib (4.2.1 - 1000.11.42) <1223BA92-5392-33F4-893F-8C20A5D0905D> /Applications/Docker.app/Contents/Frameworks/libswiftAppKit.dylib
0x104041000 - 0x1043d3ff7 +libswiftCore.dylib (4.2.1 - 1000.11.42) <D0C86227-BFC8-30D7-93B8-9F228E0F15BA> /Applications/Docker.app/Contents/Frameworks/libswiftCore.dylib
0x1046ad000 - 0x1046b5fff +libswiftCoreData.dylib (4.2.1 - 1000.11.42) <6CC602C0-1AA9-3DD3-B843-CD1D07C36F27> /Applications/Docker.app/Contents/Frameworks/libswiftCoreData.dylib
0x1046c7000 - 0x1046cafff +libswiftCoreFoundation.dylib (4.2.1 - 1000.11.42) <801E1416-6C23-3C48-BF46-2349B9F36C9E> /Applications/Docker.app/Contents/Frameworks/libswiftCoreFoundation.dylib
0x1046d3000 - 0x1046e2ff7 +libswiftCoreGraphics.dylib (4.2.1 - 1000.11.42) <579D172D-0873-33EB-A529-742D5D70BD74> /Applications/Docker.app/Contents/Frameworks/libswiftCoreGraphics.dylib
0x104707000 - 0x10470cff7 +libswiftCoreImage.dylib (4.2.1 - 1000.11.42) <4DB8ED84-0EBB-3922-B3A4-82EE4834549B> /Applications/Docker.app/Contents/Frameworks/libswiftCoreImage.dylib
0x104719000 - 0x104721fff +libswiftDarwin.dylib (4.2.1 - 1000.11.42) <70D5D45B-0327-352C-BDCE-F792699DAB88> /Applications/Docker.app/Contents/Frameworks/libswiftDarwin.dylib
0x10473b000 - 0x104754ff7 +libswiftDispatch.dylib (4.2.1 - 1000.11.42) <E8DBE923-0513-3FE8-8E3A-5778014FD810> /Applications/Docker.app/Contents/Frameworks/libswiftDispatch.dylib
0x10479a000 - 0x104902fff +libswiftFoundation.dylib (4.2.1 - 1000.11.42) <2252DB9E-6B26-31AD-A869-9D92FA2BE196> /Applications/Docker.app/Contents/Frameworks/libswiftFoundation.dylib
0x104aa2000 - 0x104aa5fff +libswiftIOKit.dylib (4.2.1 - 1000.11.42) <575A9454-3EB8-3314-B67B-9D0C88C03D5F> /Applications/Docker.app/Contents/Frameworks/libswiftIOKit.dylib
0x104ab4000 - 0x104abdfff +libswiftMetal.dylib (4.2.1 - 1000.11.42) <A538B219-717C-30F5-BB27-BF1C170EE99F> /Applications/Docker.app/Contents/Frameworks/libswiftMetal.dylib
0x104ad3000 - 0x104ad7fff +libswiftObjectiveC.dylib (4.2.1 - 1000.11.42) <A521AAA2-3B1F-38AF-BFA0-BB02A94ECA8B> /Applications/Docker.app/Contents/Frameworks/libswiftObjectiveC.dylib
0x104ae2000 - 0x104ae8ff7 +libswiftQuartzCore.dylib (4.2.1 - 1000.11.42) <C619FC2F-405B-3E38-8FDA-36B2A9EBA0F2> /Applications/Docker.app/Contents/Frameworks/libswiftQuartzCore.dylib
0x104af3000 - 0x104af6fff +libswiftXPC.dylib (4.2.1 - 1000.11.42) <3EC739CE-A1AC-3199-8461-9CA872E2B9EF> /Applications/Docker.app/Contents/Frameworks/libswiftXPC.dylib
0x104b00000 - 0x104b07fff +libswiftos.dylib (4.2.1 - 1000.11.42) <0B29ACF1-EFFD-3F02-B509-5210DC92DD31> /Applications/Docker.app/Contents/Frameworks/libswiftos.dylib
0x107c3f000 - 0x107c42047 libobjc-trampolines.dylib (787.1) <88F9B648-C455-36F8-BBB9-7D1A9F57D073> /usr/lib/libobjc-trampolines.dylib
0x10c0a3000 - 0x10c134f47 dyld (750.6) <34A11073-9E4C-38C3-9293-7D566ABAE8B6> /usr/lib/dyld
0x7fff294ca000 - 0x7fff295f8ff8 com.apple.AMDMTLBronzeDriver (3.10.15 - 3.1.0) <533CD5F2-FE9D-3220-B542-DCB01387C22F> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
0x7fff2eb88000 - 0x7fff2ef87ff1 com.apple.driver.AppleIntelKBLGraphicsMTLDriver (14.7.8 - 14.0.7) <90F7787D-4D80-3D02-BB9E-ADB2D3DFE8BC> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver
0x7fff31e0f000 - 0x7fff31e0ffff com.apple.Accelerate (1.11 - Accelerate 1.11) <4F9977AE-DBDB-3A16-A536-AC1F9938DCDD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff31e10000 - 0x7fff31e26fef libCGInterfaces.dylib (524.2.1) <DE4EE08A-4A60-398A-8E93-BB6A4B3C72FC> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
0x7fff31e27000 - 0x7fff3247dfff com.apple.vImage (8.1 - 524.2.1) <EA6F5FF2-7A1B-35D5-A5A3-D2B3386ECB75> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x7fff3247e000 - 0x7fff326e5ff7 libBLAS.dylib (1303.60.1) <C6C2D42F-7456-3DBF-8BE2-9AA06EFC78FD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x7fff326e6000 - 0x7fff32bb9fef libBNNS.dylib (144.100.2) <99C61C48-B14C-3DA6-8C31-6BF72DA0A3A9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
0x7fff32bba000 - 0x7fff32f55fff libLAPACK.dylib (1303.60.1) <5E3E3867-50C3-3E6A-9A2E-007CE77A4641> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x7fff32f56000 - 0x7fff32f6bfec libLinearAlgebra.dylib (1303.60.1) <3D433800-0099-33E0-8C81-15F83247B2C9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
0x7fff32f6c000 - 0x7fff32f71ff3 libQuadrature.dylib (7) <371F36A7-B12F-363E-8955-F24F7C2048F6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
0x7fff32f72000 - 0x7fff32fe2fff libSparse.dylib (103) <B8A10D0C-4577-343D-B310-A3E81265D107> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
0x7fff32fe3000 - 0x7fff32ff5fef libSparseBLAS.dylib (1303.60.1) <B147FEF6-A0DB-3830-BF06-45BEC58DB576> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
0x7fff32ff6000 - 0x7fff331cdfd7 libvDSP.dylib (735.140.1) <D63DC0A5-B8B4-3562-A574-E73BC3B57407> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x7fff331ce000 - 0x7fff33290fef libvMisc.dylib (735.140.1) <3601FDE3-B142-398D-987D-8151A51F0A96> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x7fff33291000 - 0x7fff33291fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <F6C5613D-2284-342B-9160-9731F78B4DE5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff33292000 - 0x7fff332f1ff0 com.apple.Accounts (113 - 113) <5805A70A-4AF8-36C4-92A6-D5AB5B4C1630> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts
0x7fff3343b000 - 0x7fff341fbff2 com.apple.AppKit (6.9 - 1894.60.100) <C4208642-19F7-3EAA-AACD-3B836FFDEFCF> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff3424b000 - 0x7fff3424bfff com.apple.ApplicationServices (48 - 50) <D4320505-6458-38FD-81F0-406F2F0A4039> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x7fff3424c000 - 0x7fff342b7fff com.apple.ApplicationServices.ATS (377 - 493.0.4.1) <CF994162-0F34-368D-BED4-D63270E35B5A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x7fff34350000 - 0x7fff3438eff0 libFontRegistry.dylib (274.0.5.1) <EAA136DE-69AC-3355-AED3-830018151715> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x7fff343e9000 - 0x7fff34418fff com.apple.ATSUI (1.0 - 1) <1FC04DE6-E0D4-3E6B-9AB6-255AB70DC9F4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI
0x7fff34419000 - 0x7fff3441dffb com.apple.ColorSyncLegacy (4.13.0 - 1) <61F37728-FDCF-314B-B75D-5CD15AB7D4D9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
0x7fff344b7000 - 0x7fff3450effa com.apple.HIServices (1.22 - 676) <9FB74637-448B-3437-B8C1-2C354264A163> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x7fff3450f000 - 0x7fff3451dfff com.apple.LangAnalysis (1.7.0 - 1.7.0) <A52FB48C-5C39-32FB-9637-9EEA7EA5CA6E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff3451e000 - 0x7fff34563ffa com.apple.print.framework.PrintCore (15.4 - 516.2) <B70D9E5A-C1D5-3159-A197-4F09E25E18C4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x7fff34564000 - 0x7fff3456eff7 com.apple.QD (4.0 - 413) <5CEBC510-0B39-3BB5-B951-3B8F5E82C3CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x7fff3456f000 - 0x7fff3457cffc com.apple.speech.synthesis.framework (9.0.24 - 9.0.24) <59947616-D486-3963-A12D-9DEF153296CD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff3457d000 - 0x7fff3465effa com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <6BD0970D-7FD8-341D-8D82-0B3BBB565462> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff34660000 - 0x7fff34660fff com.apple.audio.units.AudioUnit (1.14 - 1.14) <C8F9CC56-F7CF-3E77-B6FC-BD8E1D19FA92> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff349f7000 - 0x7fff34d86ffa com.apple.CFNetwork (1128.0.1 - 1128.0.1) <C524C617-2CEF-340C-8CE2-98EAF91CF6A8> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff34e02000 - 0x7fff34e02fff com.apple.Carbon (160 - 162) <FB72FB7D-5985-3D9C-82DB-A729FCA1249A> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff34e03000 - 0x7fff34e06ff3 com.apple.CommonPanels (1.2.6 - 101) <B2F7737D-027B-3FFA-9927-EF105CB73193> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x7fff34e07000 - 0x7fff350fbff3 com.apple.HIToolbox (2.1.1 - 994.6) <DE6F9A20-8AF7-3963-82E1-4756C4A7A54C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x7fff350fc000 - 0x7fff350ffff3 com.apple.help (1.3.8 - 71) <EAFE0E80-DABA-31D9-AC32-87A0A37C70CE> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x7fff35100000 - 0x7fff35105ff7 com.apple.ImageCapture (9.0 - 1600.65) <1A1F320E-3E85-3F3D-8AE0-B238C4E92D40> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x7fff35106000 - 0x7fff35106fff com.apple.ink.framework (10.15 - 227) <E3570EA0-7D2D-31F8-B87A-08AD80199E0D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x7fff35107000 - 0x7fff35121ffa com.apple.openscripting (1.7 - 185.1) <5012E208-2295-3169-B452-1A99E7CB36F9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x7fff35142000 - 0x7fff35142fff com.apple.print.framework.Print (15 - 271) <5B6DCE6F-FCB9-3502-897E-C54D7749B704> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x7fff35143000 - 0x7fff35145ff7 com.apple.securityhi (9.0 - 55008) <B9CF91DA-6AE8-3250-B8B1-56EF4A68755F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x7fff35146000 - 0x7fff3514cfff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <16D2AB1F-1E22-37D6-B0B6-350D79796E10> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x7fff352e6000 - 0x7fff352e6fff com.apple.Cocoa (6.11 - 23) <2F5C8ABA-711F-316C-BB97-921122AEE4DF> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff352f4000 - 0x7fff353eafff com.apple.ColorSync (4.13.0 - 3394.9) <0EE6A103-7283-3706-877D-1487BF11BBA3> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x7fff356d5000 - 0x7fff35bdeffb com.apple.audio.CoreAudio (5.0 - 5.0) <F816D92C-9408-3279-90BC-C23B69DC75AE> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff35c31000 - 0x7fff35c69fff com.apple.CoreBluetooth (1.0 - 1) <0CD1AE39-EACA-374A-9732-66798388EA91> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
0x7fff35c6a000 - 0x7fff36054fe8 com.apple.CoreData (120 - 977.3) <94F498B0-3AFB-3F8C-83E3-A8F7A1176248> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x7fff36055000 - 0x7fff36187ff6 com.apple.CoreDisplay (1.0 - 186.6.15) <599EB1B7-552C-36F7-9924-177E700079C4> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
0x7fff36188000 - 0x7fff36607feb com.apple.CoreFoundation (6.9 - 1677.104) <C0D70026-EDBE-3CBD-B317-367CF4F1C92F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff36609000 - 0x7fff36c7eff8 com.apple.CoreGraphics (2.0 - 1355.22) <4A3CDE7B-4578-3058-966A-3D1DC095A935> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff36c8c000 - 0x7fff36fe7ff0 com.apple.CoreImage (15.0.0 - 940.9) <103E76AC-A255-3B74-AD5B-46D28A904893> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
0x7fff373a8000 - 0x7fff37483ffc com.apple.CoreMedia (1.0 - 2625.9) <A3FF3AFC-8C1C-36E5-9179-66D8F075EE35> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
0x7fff37570000 - 0x7fff37570fff com.apple.CoreServices (1069.24 - 1069.24) <AA140158-E909-34C2-B2F5-20EBC93E0056> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff37571000 - 0x7fff375f6fff com.apple.AE (838.1 - 838.1) <9F7FDA11-AA47-3FF4-80D6-32A5335555DF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x7fff375f7000 - 0x7fff378d8ff7 com.apple.CoreServices.CarbonCore (1217 - 1217) <C1521E48-5E78-364A-8FA6-C4049CA4C66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x7fff378d9000 - 0x7fff37926ffd com.apple.DictionaryServices (1.2 - 323.6) <78832B5D-E126-3E28-89EC-8CA69AC5DD47> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x7fff37927000 - 0x7fff3792fff7 com.apple.CoreServices.FSEvents (1268.100.1 - 1268.100.1) <29909C83-DF5F-3751-A35B-405860DBA937> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
0x7fff37930000 - 0x7fff37b6aff6 com.apple.LaunchServices (1069.24 - 1069.24) <4760C0FA-6EDB-3CE4-AD62-5C4520A7D90B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x7fff37b6b000 - 0x7fff37c03ff1 com.apple.Metadata (10.7.0 - 2076.7) <0973F7E5-D58C-3574-A3CE-4F12CAC2D4C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x7fff37c04000 - 0x7fff37c31fff com.apple.CoreServices.OSServices (1069.24 - 1069.24) <4A42E711-6617-353A-B7DC-3F7AAF815A16> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x7fff37c32000 - 0x7fff37c99fff com.apple.SearchKit (1.4.1 - 1.4.1) <757DA392-8E1A-3266-AF15-09B79B036621> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x7fff37c9a000 - 0x7fff37cbeff5 com.apple.coreservices.SharedFileList (131.4 - 131.4) <5F518E73-EA2F-389A-A924-046374F5F15B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
0x7fff37fe3000 - 0x7fff3819affc com.apple.CoreText (643.1.5.1 - 643.1.5.1) <9C7FBD03-3845-3E2B-94B8-B3110180D3F5> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
0x7fff3819b000 - 0x7fff381dfffb com.apple.CoreVideo (1.8 - 344.3) <2F1DC859-A2E4-3983-8047-97BC0E8C55CE> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff381e0000 - 0x7fff3826dffc com.apple.framework.CoreWLAN (13.0 - 1601.2) <6C76A9E0-430F-3B3C-AE8A-3005F8E6FCFF> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
0x7fff38504000 - 0x7fff3850afff com.apple.DiskArbitration (2.7 - 2.7) <63923E3F-1489-3762-B5EB-5CE28A35FF50> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff386ff000 - 0x7fff3882dff6 com.apple.FileProvider (304.1 - 304.1) <3BC3B7F7-A568-3D99-B654-F5F2379F1560> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider
0x7fff38845000 - 0x7fff38c0afff com.apple.Foundation (6.9 - 1677.104) <2EF4C4DA-423B-3AFE-ACD1-7DAE64E47603> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff38c77000 - 0x7fff38cc7ff7 com.apple.GSS (4.0 - 2.0) <CBD56CC8-237D-3831-BF95-7672BEA768C0> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x7fff38dc2000 - 0x7fff38dc6ff3 com.apple.Hypervisor (1.0 - 1) <D38AD2E7-4332-3DB9-BDB8-301CFA517695> /System/Library/Frameworks/Hypervisor.framework/Versions/A/Hypervisor
0x7fff38e04000 - 0x7fff38f18ff3 com.apple.Bluetooth (7.0.6 - 7.0.6f7) <CF9CEFBA-97AC-3474-93AF-863C2C74C645> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
0x7fff38f7e000 - 0x7fff39022ff3 com.apple.framework.IOKit (2.0.2 - 1726.140.1) <31CA30A9-B32D-37A8-B5C8-20999D5D51BF> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff39024000 - 0x7fff39035ffb com.apple.IOSurface (269.11 - 269.11) <3423901A-0ED1-352C-BB6D-5C788C3348DA> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x7fff390b4000 - 0x7fff39210fee com.apple.ImageIO.framework (3.3.0 - 1976.11) <C17C7280-54F6-3750-85CE-C43428256D62> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x7fff39211000 - 0x7fff39214fff libGIF.dylib (1976.11) <7F53F2C2-0F2B-3308-9E90-F043F43DAB32> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x7fff39215000 - 0x7fff392ceff7 libJP2.dylib (1976.11) <EAAE8D93-7C00-347A-BF6F-C262557C0A1C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x7fff392cf000 - 0x7fff392f2fe3 libJPEG.dylib (1976.11) <47540108-F321-35F9-A98A-784E4D4F3C15> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x7fff39570000 - 0x7fff3958afef libPng.dylib (1976.11) <DDBB2E46-7BCB-339B-883E-67B97A7614A3> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x7fff3958b000 - 0x7fff3958cfff libRadiance.dylib (1976.11) <C8998674-DCB4-3C2C-9D6E-C0809D7727A2> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x7fff3958d000 - 0x7fff395d3fff libTIFF.dylib (1976.11) <79E99768-71D7-3EA9-9675-95EFACF32FC8> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x7fff39a7e000 - 0x7fff3ab1efe9 com.apple.JavaScriptCore (15609 - 15609.3.5.1.3) <1874AA53-2C73-3DB2-A98F-69D9BDB3ADC8> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x7fff3ab35000 - 0x7fff3ab47ff3 com.apple.Kerberos (3.0 - 1) <FE4E83D2-D943-3742-957D-BF6AA9E50B81> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x7fff3ab48000 - 0x7fff3ab48fff libHeimdalProxy.dylib (77) <0A2905EE-9533-3345-AF9B-AAC71513BDFD> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib
0x7fff3ac93000 - 0x7fff3acb5ffc com.apple.CoreAuthentication.SharedUtils (1.0 - 693.140.3) <A6C6FA0F-83C4-360F-96C6-1393FE6B8123> /System/Library/Frameworks/LocalAuthentication.framework/Support/SharedUtils.framework/Versions/A/SharedUtils
0x7fff3acb6000 - 0x7fff3acccff2 com.apple.LocalAuthentication (1.0 - 693.140.3) <5D391FD1-391B-390A-BBC1-62A537C8DAFE> /System/Library/Frameworks/LocalAuthentication.framework/Versions/A/LocalAuthentication
0x7fff3aeda000 - 0x7fff3aee4ffb com.apple.MediaAccessibility (1.0 - 125.1) <35B667D6-A924-3DD1-9390-234F6D12E1C0> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
0x7fff3b6ff000 - 0x7fff3b7c9fff com.apple.Metal (212.8 - 212.8) <7A496C57-4ECE-337F-96D4-09F24C033913> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
0x7fff3b7e6000 - 0x7fff3b823ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <7EBAC15D-7837-395D-B405-1E29F7DA68FA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
0x7fff3b824000 - 0x7fff3b8aefe2 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <B424FE0C-6E90-3BFA-A6E7-DD86C735AE90> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
0x7fff3b8af000 - 0x7fff3b8d4ff4 com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <02006D92-E2AB-3892-A96B-37F6520C19BA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
0x7fff3b8d5000 - 0x7fff3b8eaffb com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <CAA5A368-DB71-34F6-AEF9-27A8BC298F53> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray
0x7fff3b8eb000 - 0x7fff3ba49ffc com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <05612E06-50CB-318F-9F8E-EF4D49FAB3B0> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
0x7fff3ba4a000 - 0x7fff3ba99ff4 com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B0B591F8-6875-351E-867F-8EB3CD38CD52> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
0x7fff3ba9a000 - 0x7fff3ba9bff5 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <F2921F9A-3041-3495-878D-64134267B847> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
0x7fff3cb29000 - 0x7fff3cb35ffe com.apple.NetFS (6.0 - 4.0) <024195B7-00F1-30D3-A407-11DC3E262C05> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff3cb36000 - 0x7fff3cc8dff3 com.apple.Network (1.0 - 1) <2B933C30-E71F-3ECC-8DBD-FBBB997A6FDC> /System/Library/Frameworks/Network.framework/Versions/A/Network
0x7fff3f6bf000 - 0x7fff3f717fff com.apple.opencl (3.5 - 3.5) <983E7D45-6C6D-35EC-A68D-6AD5FCFE2356> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff3f718000 - 0x7fff3f734fff com.apple.CFOpenDirectory (10.15 - 220.40.1) <1C7F51F3-43D9-3E4A-93C9-A74C6BCAE2CE> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
0x7fff3f735000 - 0x7fff3f740ffd com.apple.OpenDirectory (10.15 - 220.40.1) <3BB64E34-C2D9-3172-BBD8-D360FE4B2737> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff400a6000 - 0x7fff400a8fff libCVMSPluginSupport.dylib (17.10.22) <2B6C3C16-3F5F-36A8-8070-2A862B90328B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
0x7fff400a9000 - 0x7fff400aefff libCoreFSCache.dylib (176.15) <E9A20E72-B17F-33D6-8894-41934A10B822> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
0x7fff400af000 - 0x7fff400b3fff libCoreVMClient.dylib (176.15) <018A48BA-1326-3847-8FB5-A7C99322EB87> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
0x7fff400b4000 - 0x7fff400bcff7 libGFXShared.dylib (17.10.22) <A530A704-1D22-3692-8DFF-EDF6A12E59F0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
0x7fff400bd000 - 0x7fff400c7fff libGL.dylib (17.10.22) <FB5E6A75-398E-38EF-8CB2-59F5BFE3034C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x7fff400c8000 - 0x7fff400fcff7 libGLImage.dylib (17.10.22) <9A3FE633-61B8-3CC7-8183-62960109401A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x7fff40292000 - 0x7fff402cefff libGLU.dylib (17.10.22) <D8B4D804-7323-30BC-871C-B7236FFC2FE3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x7fff40d0a000 - 0x7fff40d19ff7 com.apple.opengl (17.10.22 - 17.10.22) <E75C69AE-61EA-32D5-B58D-30022D68CC66> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff41cd7000 - 0x7fff41f5affb com.apple.QuartzCore (1.11 - 841.4) <FE927B0E-BD49-32CC-8A55-90F553C86C15> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff42adb000 - 0x7fff42e24ff1 com.apple.security (7.0 - 59306.140.5) <EB9E9E2A-B53B-36EE-B9CE-EEB99B603CB1> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff42e25000 - 0x7fff42eadffb com.apple.securityfoundation (6.0 - 55236.60.1) <407FE3EC-3EC2-31DF-B988-43B13D6D4A75> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
0x7fff42eae000 - 0x7fff42edbff7 com.apple.securityinterface (10.0 - 55139.120.1) <6C6C69FE-E0BB-3D9B-A320-F13FC296C06C> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInterface
0x7fff42edc000 - 0x7fff42ee0ff8 com.apple.xpc.ServiceManagement (1.0 - 1) <279E7AA9-B23D-3E32-946B-5559EDC56C86> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
0x7fff43b8c000 - 0x7fff43c06ff7 com.apple.SystemConfiguration (1.19 - 1.19) <84F9B3BB-F7AF-3B7C-8CD0-D3C22D19619F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x7fff43e86000 - 0x7fff44209ff4 com.apple.VideoToolbox (1.0 - 2625.9) <6CF18E28-A7A8-3952-8171-7E4FF4FB37FA> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
0x7fff444ab000 - 0x7fff44c48fe7 libwebrtc.dylib (7609.3.5.1.3) <855537EC-FD8A-3C05-8BE0-0AA41AF99BD6> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libwebrtc.dylib
0x7fff44c49000 - 0x7fff46eb3ff3 com.apple.WebCore (15609 - 15609.3.5.1.3) <864EB027-E098-38BD-A5D4-17FAC53213CD> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
0x7fff46eb4000 - 0x7fff470c0ffb com.apple.WebKitLegacy (15609 - 15609.3.5.1.3) <1F65CF17-D985-3743-8993-36B1D06ECBE9> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebKitLegacy.framework/Versions/A/WebKitLegacy
0x7fff470c1000 - 0x7fff477c6ffd com.apple.WebKit (15609 - 15609.3.5.1.3) <77FB3BFF-DF46-3261-8A74-EAB7AF8BDB4D> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x7fff47b76000 - 0x7fff47c3bfe7 com.apple.APFS (1412.141.1 - 1412.141.1) <C86A3423-E61C-335A-9D17-0B3CE5BB6467> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
0x7fff48287000 - 0x7fff48292ffc com.apple.accessibility.AXCoreUtilities (1.0 - 1) <CD025BEB-6E7B-3F08-A433-2FB12299371C> /System/Library/PrivateFrameworks/AXCoreUtilities.framework/Versions/A/AXCoreUtilities
0x7fff48403000 - 0x7fff4840bff5 com.apple.AccessibilityBundles (1.0 - 131.5) <D431EB06-AE4E-3B49-A99D-50BF85E13741> /System/Library/PrivateFrameworks/AccessibilityBundles.framework/Versions/A/AccessibilityBundles
0x7fff48d50000 - 0x7fff48d51ff1 com.apple.AggregateDictionary (1.0 - 1) <2E60E192-E839-3366-804D-9739E79CBC9F> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
0x7fff492eb000 - 0x7fff49308ff4 com.apple.AppContainer (4.0 - 448.100.6) <EF924755-FFB9-34D4-B639-054714E5F26D> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer
0x7fff4932a000 - 0x7fff49340ff3 com.apple.AppSSOCore (1.0 - 1) <05C509DA-F6D6-3290-9CBB-AF837EC2C6DC> /System/Library/PrivateFrameworks/AppSSOCore.framework/Versions/A/AppSSOCore
0x7fff4935d000 - 0x7fff4936bff7 com.apple.AppSandbox (4.0 - 448.100.6) <BD6E612B-FECD-3024-9143-E437839F1F5D> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox
0x7fff49756000 - 0x7fff497bbff7 com.apple.AppSupport (1.0.0 - 29) <4819B5D3-7FB8-336A-81D5-63E0850A391C> /System/Library/PrivateFrameworks/AppSupport.framework/Versions/A/AppSupport
0x7fff497e7000 - 0x7fff4980bffb com.apple.framework.Apple80211 (13.0 - 1610.1) <C53B760A-3305-3053-9BBE-BB70AE3C349B> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
0x7fff49ac9000 - 0x7fff49ad8fd7 com.apple.AppleFSCompression (119.100.1 - 1.0) <B0E6D541-1850-384B-B397-CC73503C20B2> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
0x7fff49bd7000 - 0x7fff49be2ff7 com.apple.AppleIDAuthSupport (1.0 - 1) <8D12CC19-2D08-3F37-93E3-3D170E6EC78A> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
0x7fff49c24000 - 0x7fff49c6cff7 com.apple.AppleJPEG (1.0 - 1) <6D4A6930-F0E2-3CFF-916F-06E87E648069> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
0x7fff4a05b000 - 0x7fff4a07dfff com.apple.applesauce (1.0 - 16.25) <68E0364C-AEA7-3654-A030-136BF3CD92F3> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
0x7fff4a13c000 - 0x7fff4a13fffb com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <D51FE050-B5D0-3E07-8CAE-730C3C7815D4> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
0x7fff4a140000 - 0x7fff4a190ff7 com.apple.AppleVAFramework (6.1.2 - 6.1.2) <73FB7981-5BEC-3546-BE46-D8F15FD8FA92> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x7fff4a1d9000 - 0x7fff4a1e8ff9 com.apple.AssertionServices (1.0 - 223.140.2) <F86E0D38-3E0E-37B2-A070-4176E533040D> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
0x7fff4ad7c000 - 0x7fff4afbcfe0 com.apple.audio.AudioToolboxCore (1.0 - 1104.93) <5B539F50-93E8-3F73-9E4C-678C85D0488F> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore
0x7fff4afc0000 - 0x7fff4b0dcfff com.apple.AuthKit (1.0 - 1) <D7FBDAA7-B582-33C0-9030-31169A53A542> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
0x7fff4b299000 - 0x7fff4b2a2ff7 com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <AED997B4-B67E-3216-AA6D-5BB5216905E6> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
0x7fff4b2a3000 - 0x7fff4b344ff5 com.apple.backup.framework (1.11.6 - 1298.6.2) <EE699538-4D97-30D2-BAA1-C35C96C7BE83> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0x7fff4b345000 - 0x7fff4b3d1ff6 com.apple.BaseBoard (466.3 - 466.3) <CEADF75A-0A22-350B-8476-A612ED386E24> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
0x7fff4b4d3000 - 0x7fff4b50fff7 com.apple.bom (14.0 - 219.2) <83788F83-9B27-3208-9155-95EA440CAEC7> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x7fff4c08f000 - 0x7fff4c0defff com.apple.ChunkingLibrary (307 - 307) <F0CB2422-B138-36BA-ADD5-58D95D086FEA> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
0x7fff4cf8a000 - 0x7fff4cf9affb com.apple.CommonAuth (4.0 - 2.0) <CF67FF34-4238-3ECA-B4A4-EA04F18A0D36> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x7fff4cfae000 - 0x7fff4cfc5fff com.apple.commonutilities (8.0 - 900) <C7826C15-66EF-365D-B3BD-D2E2BF3564DC> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities
0x7fff4daf2000 - 0x7fff4db13ff4 com.apple.analyticsd (1.0 - 1) <E6E3B6EA-A2BE-3752-B06D-BECCBA4E85B2> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics
0x7fff4e0aa000 - 0x7fff4e0baff3 com.apple.CoreEmoji (1.0 - 107.1) <7374E3E4-907B-3691-ABAB-F7A27CCCF650> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
0x7fff4e6fa000 - 0x7fff4e764ff0 com.apple.CoreNLP (1.0 - 213) <BD3A01B7-9C7E-3ABF-B0B5-6D1131C95871> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP
0x7fff4ea22000 - 0x7fff4ea26ffb com.apple.CoreOptimization (1.0 - 1) <0FFD7AA1-6E0B-395B-BCDC-73C1CCECC25B> /System/Library/PrivateFrameworks/CoreOptimization.framework/Versions/A/CoreOptimization
0x7fff4eb92000 - 0x7fff4eb9aff8 com.apple.CorePhoneNumbers (1.0 - 1) <E4DAD514-0B3B-3E0B-8AEA-39B320FAAF03> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers
0x7fff4eb9b000 - 0x7fff4ebed94b com.apple.CorePrediction (1.0 - 1) <FEE0DD88-AE3C-3292-BF94-395701BEA87C> /System/Library/PrivateFrameworks/CorePrediction.framework/Versions/A/CorePrediction
0x7fff4f587000 - 0x7fff4f5aafff com.apple.CoreSVG (1.0 - 129.3) <F38189F9-C8F9-3D62-9D5F-3F520FB81724> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG
0x7fff4f5ab000 - 0x7fff4f5defff com.apple.CoreServicesInternal (446.7 - 446.7) <93E6988C-F805-3939-AB8D-584ABADFD34E> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
0x7fff4f5df000 - 0x7fff4f60dffd com.apple.CSStore (1069.24 - 1069.24) <ADE95A95-498F-3B41-8377-8B4896265A73> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore
0x7fff4fb32000 - 0x7fff4fbc8ff7 com.apple.CoreSymbolication (11.4 - 64535.33.2) <A56D680A-DDF4-3184-A55E-5B2B5C12B1C5> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
0x7fff4fc60000 - 0x7fff4fd8cff6 com.apple.coreui (2.1 - 609.4) <5812AEFB-5C84-37F1-868F-2DDBC3CDF930> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x7fff4fd8d000 - 0x7fff4ff46ffa com.apple.CoreUtils (6.2.4 - 624.7) <456CC907-E838-3945-B70A-66E862C19CD6> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
0x7fff50080000 - 0x7fff50093ff1 com.apple.CrashReporterSupport (10.13 - 15016) <B9B5F954-A6FA-349F-973C-8B49711F9A42> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
0x7fff5014c000 - 0x7fff5015eff8 com.apple.framework.DFRFoundation (1.0 - 252.50.1) <F7FCE163-8165-398F-87BC-B2FA8A5F9857> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation
0x7fff5015f000 - 0x7fff50164fff com.apple.DSExternalDisplay (3.1 - 380) <8EA5D569-3662-3303-B2BA-3973B8A1AAD8> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay
0x7fff501ee000 - 0x7fff50268ff0 com.apple.datadetectorscore (8.0 - 659) <146BE183-0031-37C6-AD62-23EF68697F45> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
0x7fff502b4000 - 0x7fff502f1ff8 com.apple.DebugSymbols (194 - 194) <0873DC37-076B-31E6-A82F-B36D874FE5C9> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
0x7fff502f2000 - 0x7fff5047aff6 com.apple.desktopservices (1.14.5 - 1281.5.3) <BE6F44A8-FF2E-3E26-A06B-BB57EC233612> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x7fff50490000 - 0x7fff5049cff8 com.apple.DeviceIdentity (1.0 - 1) <7638347F-B710-3C34-A883-2731404C1727> /System/Library/PrivateFrameworks/DeviceIdentity.framework/Versions/A/DeviceIdentity
0x7fff51e3b000 - 0x7fff52256ff1 com.apple.vision.FaceCore (4.3.0 - 4.3.0) <B2FDE1D6-38F0-3E1A-9C6B-8F2E325308C4> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
0x7fff528f5000 - 0x7fff52a2cff4 libFontParser.dylib (277.2.6.1) <9E9E2EAA-3273-360E-A01B-EB986ECB7BCF> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib
0x7fff52a2d000 - 0x7fff52a61fff libTrueTypeScaler.dylib (277.2.6.1) <F8A27F0F-44B3-3A1E-8B75-2DFD4A90E1D4> /System/Library/PrivateFrameworks/FontServices.framework/libTrueTypeScaler.dylib
0x7fff52ac6000 - 0x7fff52ad6ff6 libhvf.dylib (1.0 - 277.2.6.1) <1605B441-08E0-332D-B7D8-0E13F37B54E7> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib
0x7fff55fb7000 - 0x7fff55fb8fff libmetal_timestamp.dylib (902.14.11) <7A1B20F8-498D-3D01-8B89-14B7DC9C56CA> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib
0x7fff57672000 - 0x7fff57678fff com.apple.GPUWrangler (5.2.6 - 5.2.6) <0D2C7F42-7C4E-3ED4-A4B1-D5383840D23E> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler
0x7fff57997000 - 0x7fff579bdff1 com.apple.GenerationalStorage (2.0 - 314) <3479C9D7-A4B1-3E25-BCC9-7713FE0D1183> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
0x7fff58aeb000 - 0x7fff58af9ffb com.apple.GraphVisualizer (1.0 - 100.1) <F3DCDBA0-698C-3F4D-9471-13B2A10A6445> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer
0x7fff58afa000 - 0x7fff58b07ff3 com.apple.GraphicsServices (1.0 - 1.0) <D253504A-4634-30AD-BD5B-C37F91BA8103> /System/Library/PrivateFrameworks/GraphicsServices.framework/Versions/A/GraphicsServices
0x7fff58c98000 - 0x7fff58d56ff4 com.apple.Heimdal (4.0 - 2.0) <797EEF52-BA3B-3E43-9541-713376261B7E> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x7fff59753000 - 0x7fff59782ff8 com.apple.HelpData (2.3 - 199) <A1AB5BD0-8B2C-3CDD-BCCC-9CB191BBCB33> /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
0x7fff5aed2000 - 0x7fff5aedbffe com.apple.IOAccelMemoryInfo (1.0 - 1) <50DDA9C2-BDDF-33D4-9BA9-A161E99F1EAD> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo
0x7fff5aedc000 - 0x7fff5aee4ff5 com.apple.IOAccelerator (438.7.3 - 438.7.3) <49288C8C-00C0-3CA2-B347-5418B6BFA4B8> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
0x7fff5aef1000 - 0x7fff5af08fff com.apple.IOPresentment (47.10 - 37) <32F1B3BC-4644-3982-AAB2-8EB5D5FF0161> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment
0x7fff5b290000 - 0x7fff5b2dbff1 com.apple.IconServices (438.3 - 438.3) <9033B15E-5B2F-36EC-965B-C035AB6E195E> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
0x7fff5b499000 - 0x7fff5b4a0ff9 com.apple.InternationalSupport (1.0 - 45.4) <D85BD7C8-08A8-399C-BF21-C1F050F9982F> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport
0x7fff5b72d000 - 0x7fff5b74cffd com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <6F655A32-F963-3A7E-B475-E460F4AC7D99> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle
0x7fff5b881000 - 0x7fff5b94fffd com.apple.LanguageModeling (1.0 - 215.1) <0114A0C7-1FF7-3336-AAC1-A0DECA71CED6> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
0x7fff5b950000 - 0x7fff5b998fff com.apple.Lexicon-framework (1.0 - 72) <1A091676-EE6C-3393-B1B5-42A207CF0612> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon
0x7fff5b99f000 - 0x7fff5b9a4ff3 com.apple.LinguisticData (1.0 - 353.18) <3B92F249-4602-325F-984B-D2DE61EEE4E1> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData
0x7fff5cd0d000 - 0x7fff5cd59fff com.apple.spotlight.metadata.utilities (1.0 - 2076.7) <0237323B-EC78-3FBF-9FC7-5A1FE2B5CE25> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities
0x7fff5cd5a000 - 0x7fff5ce2bffa com.apple.gpusw.MetalTools (1.0 - 1) <99876E08-37D7-3828-8796-56D90C9AFBDB> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools
0x7fff5d05f000 - 0x7fff5d07dfff com.apple.MobileKeyBag (2.0 - 1.0) <E06B3F60-7A3B-3843-AB11-1CC68CC4E468> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag
0x7fff5d2e0000 - 0x7fff5d310ff7 com.apple.MultitouchSupport.framework (3440.1 - 3440.1) <3D6999BC-BD40-3B50-8DF6-FF09A876DEFF> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
0x7fff5d810000 - 0x7fff5d81afff com.apple.NetAuth (6.2 - 6.2) <E28A8847-C251-3BA6-A2C3-2A4A6B5FA18C> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff5e230000 - 0x7fff5e27bffb com.apple.OTSVG (1.0 - 643.1.5.1) <B10CC7EF-AE50-356D-A18E-0371DDDD3102> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG
0x7fff5f498000 - 0x7fff5f4a3ff2 com.apple.PerformanceAnalysis (1.243.2 - 243.2) <EABF9DF7-C9E8-3839-9822-484EF7E0530B> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
0x7fff5f4a4000 - 0x7fff5f4ccffb com.apple.persistentconnection (1.0 - 1.0) <08537EA8-12B1-3256-9B88-7624285622E2> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection
0x7fff61e8c000 - 0x7fff61ea5ffb com.apple.ProtocolBuffer (1 - 274.24.9.16.3) <B034A3C9-78B1-30A2-A7A7-30CB95C7A117> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer
0x7fff622e5000 - 0x7fff622f1ff5 com.apple.xpc.RemoteServiceDiscovery (1.0 - 1738.140.1) <0CBB148D-D7A2-3E9B-A767-558891AF3C05> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/RemoteServiceDiscovery
0x7fff62305000 - 0x7fff6232eff1 com.apple.RemoteViewServices (2.0 - 148) <2D6D1169-F880-3E74-A8DB-C057352C71BC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
0x7fff6232f000 - 0x7fff62344ffa com.apple.xpc.RemoteXPC (1.0 - 1738.140.1) <2B4F61EA-8F7C-3DBC-8FF6-25574425242D> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC
0x7fff62493000 - 0x7fff624ceff0 com.apple.RunningBoardServices (1.0 - 223.140.2) <51770481-8A56-3202-8473-04DD9013D155> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices
0x7fff631f7000 - 0x7fff63243ff9 com.apple.Safari.SafeBrowsing (15609 - 15609.3.5.1.3) <38C5E5B1-6055-324C-8CEE-BE3D337E9E5A> /System/Library/PrivateFrameworks/SafariSafeBrowsing.framework/Versions/A/SafariSafeBrowsing
0x7fff63daf000 - 0x7fff63db2ff5 com.apple.SecCodeWrapper (4.0 - 448.100.6) <487D191A-0870-390F-9A10-096EA73F9C81> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper
0x7fff63f25000 - 0x7fff6404cfff com.apple.Sharing (1526.37 - 1526.37) <4475BAED-8036-3E55-B24D-7BA49B8D41DF> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
0x7fff640a5000 - 0x7fff640c3ff2 com.apple.shortcut (2.16 - 106) <0A7179E9-1261-3538-8492-1EAB436AC037> /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
0x7fff65461000 - 0x7fff65757ff7 com.apple.SkyLight (1.600.0 - 451.4) <02B6C1E5-C6CB-3065-91EF-DE13FD4BC726> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
0x7fff65fa4000 - 0x7fff65fb2ffb com.apple.SpeechRecognitionCore (6.0.91.2 - 6.0.91.2) <791BB87B-7280-3EF3-8109-4A060C8F9368> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
0x7fff667e6000 - 0x7fff667efff7 com.apple.SymptomDiagnosticReporter (1.0 - 1238.120.1) <1BDDF257-18EA-3213-BC2E-3400C7AE4623> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter
0x7fff66aa6000 - 0x7fff66ab6ff3 com.apple.TCC (1.0 - 1) <FFC71AC3-245B-37B2-A57C-15104BF46743> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x7fff66fdb000 - 0x7fff670a1ff0 com.apple.TextureIO (3.10.9 - 3.10.9) <CDE5AE6F-4AAB-391C-A84D-9FCD9E021BBC> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO
0x7fff67271000 - 0x7fff674c9ff0 com.apple.UIFoundation (1.0 - 662) <154E8B2A-BEF7-34B3-9ACC-504820F7B032> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
0x7fff67560000 - 0x7fff67566ffe com.apple.URLFormatting (119 - 119.18) <45C5B5CD-6741-3F10-8B47-1AFE9D25F017> /System/Library/PrivateFrameworks/URLFormatting.framework/Versions/A/URLFormatting
0x7fff6813e000 - 0x7fff6815effc com.apple.UserManagement (1.0 - 1) <C146B7BF-0B06-300A-B45C-E241E447978F> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement
0x7fff68f0a000 - 0x7fff68ff4ff8 com.apple.ViewBridge (464.1 - 464.1) <6563DE9C-3639-396C-8500-52326D525DE4> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge
0x7fff6919a000 - 0x7fff6919bfff com.apple.WatchdogClient.framework (1.0 - 67.120.2) <FFA17DA1-F6DD-34D3-A708-1F73C8BA7EA7> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient
0x7fff6936e000 - 0x7fff6936efff com.apple.WebInspectorUI (15609 - 15609.3.5.1.3) <FFB409AD-E344-3CF2-B76F-0FAEAAAB46E9> /System/Library/PrivateFrameworks/WebInspectorUI.framework/Versions/A/WebInspectorUI
0x7fff6952a000 - 0x7fff69565fff libAWDSupport.dylib (949) <EBE20139-E443-30DF-BCAD-2A6A8470F631> /System/Library/PrivateFrameworks/WirelessDiagnostics.framework/Versions/A/Libraries/libAWDSupport.dylib
0x7fff69566000 - 0x7fff69846ff7 libAWDSupportFramework.dylib (3541.2) <36AEAC24-D852-31A0-A750-ACB4D3441782> /System/Library/PrivateFrameworks/WirelessDiagnostics.framework/Versions/A/Libraries/libAWDSupportFramework.dylib
0x7fff69847000 - 0x7fff69858fff libprotobuf-lite.dylib (3541.2) <578CA7D8-149E-3643-937B-DAD5501E4575> /System/Library/PrivateFrameworks/WirelessDiagnostics.framework/Versions/A/Libraries/libprotobuf-lite.dylib
0x7fff69859000 - 0x7fff698b2ffb libprotobuf.dylib (3541.2) <0CDB164D-E7C3-3D4F-BF11-47402D67D7B0> /System/Library/PrivateFrameworks/WirelessDiagnostics.framework/Versions/A/Libraries/libprotobuf.dylib
0x7fff698b3000 - 0x7fff698f7ff6 com.apple.awd (1.0 - 949) <9DA8A821-4354-3E24-BAA1-4519D2279F2B> /System/Library/PrivateFrameworks/WirelessDiagnostics.framework/Versions/A/WirelessDiagnostics
0x7fff69dcb000 - 0x7fff69dceffa com.apple.dt.XCTTargetBootstrap (1.0 - 16091) <4D2C7B80-3DE8-30BD-A6F0-D59C5E8F91D9> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap
0x7fff69e48000 - 0x7fff69e56ff5 com.apple.audio.caulk (1.0 - 32.3) <DC6D48E8-F961-3B6C-9349-3D2E66522EFA> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
0x7fff6a198000 - 0x7fff6a19aff3 com.apple.loginsupport (1.0 - 1) <0E8CE493-2629-3F47-8C1A-BFA1C0B8D7EC> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
0x7fff6a19b000 - 0x7fff6a1aeffd com.apple.login (3.0 - 3.0) <C2BBE02B-BBD9-328B-ACD2-516D783A3D1F> /System/Library/PrivateFrameworks/login.framework/Versions/A/login
0x7fff6cb8c000 - 0x7fff6cba1ffe libAccessibility.dylib (2790.70) <4A7CB98C-E838-3075-97A0-3322CF3FEFF4> /usr/lib/libAccessibility.dylib
0x7fff6cc7e000 - 0x7fff6ccb1ffa libAudioToolboxUtility.dylib (1104.93) <20C66F4D-5DF3-3B07-8728-184DCDCB1248> /usr/lib/libAudioToolboxUtility.dylib
0x7fff6ccb8000 - 0x7fff6ccecfff libCRFSuite.dylib (48) <602A4F18-1783-3B69-9DB6-CCBF4703476B> /usr/lib/libCRFSuite.dylib
0x7fff6ccef000 - 0x7fff6ccf9fff libChineseTokenizer.dylib (34) <3F5BC40A-C2CA-3CBE-9D97-E257DEA6BA63> /usr/lib/libChineseTokenizer.dylib
0x7fff6cd85000 - 0x7fff6cd87ff7 libDiagnosticMessagesClient.dylib (112) <C94F3B7B-1854-38EB-9778-834501C53B3F> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff6cdcd000 - 0x7fff6cf84ffb libFosl_dynamic.dylib (100.4) <737573B2-190A-3BA1-8220-807AD0A2CE5E> /usr/lib/libFosl_dynamic.dylib
0x7fff6cfab000 - 0x7fff6cfb1ff3 libIOReport.dylib (54) <04AB2D0E-9D6B-3FA7-B838-593F67C6F85C> /usr/lib/libIOReport.dylib
0x7fff6d093000 - 0x7fff6d09afff libMatch.1.dylib (36) <5C6F3971-9D9E-3630-BDB6-60BFC5A665E0> /usr/lib/libMatch.1.dylib
0x7fff6d0c9000 - 0x7fff6d0e9ff7 libMobileGestalt.dylib (826.140.5) <B2F770D2-7AF0-39CC-B71F-314725061D82> /usr/lib/libMobileGestalt.dylib
0x7fff6d25b000 - 0x7fff6d25cfff libSystem.B.dylib (1281.100.1) <001B3B7F-D02C-31D3-B961-1ED445D5A266> /usr/lib/libSystem.B.dylib
0x7fff6d25d000 - 0x7fff6d2e8ff7 libTelephonyUtilDynamic.dylib (5017.1) <649F71B8-8B54-35AD-83C5-7A6BA4B590E6> /usr/lib/libTelephonyUtilDynamic.dylib
0x7fff6d2e9000 - 0x7fff6d2eafff libThaiTokenizer.dylib (3) <CDB63DB5-25A3-3DC7-B226-2D9E2D1EB786> /usr/lib/libThaiTokenizer.dylib
0x7fff6d302000 - 0x7fff6d318fff libapple_nghttp2.dylib (1.39.2) <07FEC48A-87CF-32A3-8194-FA70B361713A> /usr/lib/libapple_nghttp2.dylib
0x7fff6d34d000 - 0x7fff6d3bfff7 libarchive.2.dylib (72.140.1) <AC311FBA-F2DD-3595-AA76-769F912942B8> /usr/lib/libarchive.2.dylib
0x7fff6d3c0000 - 0x7fff6d459fe5 libate.dylib (3.0.1) <76EA60FB-748C-313F-8951-B076540BEA97> /usr/lib/libate.dylib
0x7fff6d45d000 - 0x7fff6d45dff3 libauto.dylib (187) <B6124448-7690-34AE-8939-ED84AAC630CE> /usr/lib/libauto.dylib
0x7fff6d45e000 - 0x7fff6d522ffe libboringssl.dylib (283.120.1) <E0BB2DBD-632C-3B2D-9155-4E256CC33C03> /usr/lib/libboringssl.dylib
0x7fff6d523000 - 0x7fff6d533ffb libbsm.0.dylib (60.100.1) <00BFFB9A-2FFE-3C24-896A-251BC61917FD> /usr/lib/libbsm.0.dylib
0x7fff6d534000 - 0x7fff6d540fff libbz2.1.0.dylib (44) <14CC4988-B6D4-3879-AFC2-9A0DDC6388DE> /usr/lib/libbz2.1.0.dylib
0x7fff6d541000 - 0x7fff6d593fff libc++.1.dylib (902.1) <59A8239F-C28A-3B59-B8FA-11340DC85EDC> /usr/lib/libc++.1.dylib
0x7fff6d594000 - 0x7fff6d5a9ffb libc++abi.dylib (902) <E692F14F-C65E-303B-9921-BB7E97D77855> /usr/lib/libc++abi.dylib
0x7fff6d5aa000 - 0x7fff6d5aafff libcharset.1.dylib (59) <72447768-9244-39AB-8E79-2FA14EC0AD33> /usr/lib/libcharset.1.dylib
0x7fff6d5ab000 - 0x7fff6d5bcfff libcmph.dylib (8) <E72A20DB-2E86-378D-A237-EB9A1370F989> /usr/lib/libcmph.dylib
0x7fff6d5bd000 - 0x7fff6d5d4fd7 libcompression.dylib (87) <64C91066-586D-38C0-A2F3-3E60A940F859> /usr/lib/libcompression.dylib
0x7fff6d8ae000 - 0x7fff6d8c4ff7 libcoretls.dylib (167) <770A5B96-936E-34E3-B006-B1CEC299B5A5> /usr/lib/libcoretls.dylib
0x7fff6d8c5000 - 0x7fff6d8c6fff libcoretls_cfhelpers.dylib (167) <ED52EF99-04FC-3576-9E96-DBA416154838> /usr/lib/libcoretls_cfhelpers.dylib
0x7fff6de83000 - 0x7fff6dee2ff7 libcups.2.dylib (483.6) <1067A7A0-4FDC-3873-97DC-31AC0E6A7DFE> /usr/lib/libcups.2.dylib
0x7fff6dfec000 - 0x7fff6dfecfff libenergytrace.dylib (21) <162DFCC0-8F48-3DD0-914F-FA8653E27B26> /usr/lib/libenergytrace.dylib
0x7fff6dfed000 - 0x7fff6e005fff libexpat.1.dylib (19.60.2) <FED7C38B-92D8-342D-AED7-871B12D1F7E7> /usr/lib/libexpat.1.dylib
0x7fff6e013000 - 0x7fff6e015fff libfakelink.dylib (149.1) <36146CB2-E6A5-37BB-9EE8-1B4034D8F3AD> /usr/lib/libfakelink.dylib
0x7fff6e024000 - 0x7fff6e029fff libgermantok.dylib (24) <BFAFD35B-D68C-30BF-80F2-FAEB26FB6A80> /usr/lib/libgermantok.dylib
0x7fff6e02a000 - 0x7fff6e033ff7 libheimdal-asn1.dylib (564.140.1) <0AC6FB62-2B0F-3E93-A931-E4DC4B1D757A> /usr/lib/libheimdal-asn1.dylib
0x7fff6e034000 - 0x7fff6e124fff libiconv.2.dylib (59) <18311A67-E4EF-3CC7-95B3-C0EDEE3A282F> /usr/lib/libiconv.2.dylib
0x7fff6e125000 - 0x7fff6e37cfff libicucore.A.dylib (64260.0.1) <8AC2CB07-E7E0-340D-A849-186FA1F27251> /usr/lib/libicucore.A.dylib
0x7fff6e396000 - 0x7fff6e397fff liblangid.dylib (133) <30CFC08C-EF36-3CF5-8AEA-C1CB070306B7> /usr/lib/liblangid.dylib
0x7fff6e398000 - 0x7fff6e3b0ff3 liblzma.5.dylib (16) <C131EF18-2CDD-3271-8A30-A8760D4FE166> /usr/lib/liblzma.5.dylib
0x7fff6e3c8000 - 0x7fff6e46fff7 libmecab.dylib (883.11) <2DF2B2E9-438D-326E-89C8-DD5247ABFE08> /usr/lib/libmecab.dylib
0x7fff6e470000 - 0x7fff6e6d2ff1 libmecabra.dylib (883.11) <787FF18A-7440-3C30-A10C-7A34C63D3080> /usr/lib/libmecabra.dylib
0x7fff6ea3f000 - 0x7fff6ea6efff libncurses.5.4.dylib (57) <995DFEEA-40F3-377F-B73D-D02AC59D591F> /usr/lib/libncurses.5.4.dylib
0x7fff6eb9e000 - 0x7fff6f01aff5 libnetwork.dylib (1880.120.4) <F2B8AAA5-E093-37F1-885B-EDCD9783F1C0> /usr/lib/libnetwork.dylib
0x7fff6f0bb000 - 0x7fff6f0eefde libobjc.A.dylib (787.1) <6DF81160-5E7F-3E31-AA1E-C875E3B98AF6> /usr/lib/libobjc.A.dylib
0x7fff6f101000 - 0x7fff6f105fff libpam.2.dylib (25.100.1) <0502F395-8EE6-3D2A-9239-06FD5622E19E> /usr/lib/libpam.2.dylib
0x7fff6f108000 - 0x7fff6f13eff7 libpcap.A.dylib (89.120.1) <A748C246-1484-3CBC-94DD-B4C47877AA78> /usr/lib/libpcap.A.dylib
0x7fff6f1c2000 - 0x7fff6f1dafff libresolv.9.dylib (67.40.1) <C57EDFEF-D36A-310B-8D14-8C68A625B1E8> /usr/lib/libresolv.9.dylib
0x7fff6f1dc000 - 0x7fff6f220ff7 libsandbox.1.dylib (1217.140.4) <9A1B5D3D-F30C-3FC5-8455-F4A3D067DF53> /usr/lib/libsandbox.1.dylib
0x7fff6f234000 - 0x7fff6f235ff7 libspindump.dylib (281.3) <B03C6E7D-99CB-3B79-A70E-ED24A6A1BEF5> /usr/lib/libspindump.dylib
0x7fff6f236000 - 0x7fff6f420ff7 libsqlite3.dylib (308.5) <35A2BD9F-4E33-30DE-A994-4AB585AC3AFE> /usr/lib/libsqlite3.dylib
0x7fff6f616000 - 0x7fff6f670ff8 libusrtcp.dylib (1880.120.4) <4FE72CED-B2F1-3483-B8CC-7FBF5ED04CA1> /usr/lib/libusrtcp.dylib
0x7fff6f671000 - 0x7fff6f674ffb libutil.dylib (57) <F01467F6-23A7-37EE-A170-33CE1577B41D> /usr/lib/libutil.dylib
0x7fff6f675000 - 0x7fff6f682ff7 libxar.1.dylib (425.2) <EE964412-9E25-30B3-BCC0-CCEFBCC8094B> /usr/lib/libxar.1.dylib
0x7fff6f688000 - 0x7fff6f76aff7 libxml2.2.dylib (33.4) <EFA77CC6-9139-37B3-98D4-B0E526110EE3> /usr/lib/libxml2.2.dylib
0x7fff6f76e000 - 0x7fff6f796fff libxslt.1.dylib (16.9) <34A45627-DA5B-37D2-9609-65B425E0010A> /usr/lib/libxslt.1.dylib
0x7fff6f797000 - 0x7fff6f7a9ff3 libz.1.dylib (76) <793D9643-CD83-3AAC-8B96-88D548FAB620> /usr/lib/libz.1.dylib
0x7fff6f7d4000 - 0x7fff6f7d6ff9 liblog_network.dylib (1880.120.4) <5F396C77-8B35-3C81-9457-C41590C93405> /usr/lib/log/liblog_network.dylib
0x7fff70058000 - 0x7fff7005dff3 libcache.dylib (83) <5940876E-AC8A-3BE0-80B3-DE3FB14E257A> /usr/lib/system/libcache.dylib
0x7fff7005e000 - 0x7fff70069fff libcommonCrypto.dylib (60165.120.1) <C095BD55-1D27-337F-9B02-885E1C7FF87A> /usr/lib/system/libcommonCrypto.dylib
0x7fff7006a000 - 0x7fff70071fff libcompiler_rt.dylib (101.2) <6E80AC11-A277-31FA-AEEF-E5A528274C77> /usr/lib/system/libcompiler_rt.dylib
0x7fff70072000 - 0x7fff7007bff7 libcopyfile.dylib (166.40.1) <EB5E0BC8-873D-3546-A40E-C36DC46FA8F6> /usr/lib/system/libcopyfile.dylib
0x7fff7007c000 - 0x7fff7010efdb libcorecrypto.dylib (866.140.1) <0B6C52DB-5A50-3FCD-8B5E-C0C2F35857E3> /usr/lib/system/libcorecrypto.dylib
0x7fff7021b000 - 0x7fff7025bff0 libdispatch.dylib (1173.100.2) <EAD535EE-1270-39A9-A254-95CF117FF3B0> /usr/lib/system/libdispatch.dylib
0x7fff7025c000 - 0x7fff70292fff libdyld.dylib (750.6) <24C41E8B-6B33-30C7-94C9-02D2BD051D66> /usr/lib/system/libdyld.dylib
0x7fff70293000 - 0x7fff70293ffb libkeymgr.dylib (30) <6F582FDB-EB1A-3ED2-A989-B750643E2647> /usr/lib/system/libkeymgr.dylib
0x7fff70294000 - 0x7fff702a0ff3 libkxld.dylib (6153.141.1) <756B1F0D-2E37-31A7-A6F0-2E5C22E62C3D> /usr/lib/system/libkxld.dylib
0x7fff702a1000 - 0x7fff702a1ff7 liblaunch.dylib (1738.140.1) <AFBCBDD3-0B55-3ECD-8E04-A73A3A57356B> /usr/lib/system/liblaunch.dylib
0x7fff702a2000 - 0x7fff702a7ff7 libmacho.dylib (959.0.1) <1B0296B5-3FD0-342C-BCC2-9886351A4391> /usr/lib/system/libmacho.dylib
0x7fff702a8000 - 0x7fff702aaff3 libquarantine.dylib (110.40.3) <67FE2676-F9E8-3797-AEE5-F5F9D191CFA3> /usr/lib/system/libquarantine.dylib
0x7fff702ab000 - 0x7fff702acff7 libremovefile.dylib (48) <5CEBDAB2-988A-3B66-87BC-3C45D1C08730> /usr/lib/system/libremovefile.dylib
0x7fff702ad000 - 0x7fff702c4ff3 libsystem_asl.dylib (377.60.2) <7A07FF86-658E-35D7-8136-829737E98B7B> /usr/lib/system/libsystem_asl.dylib
0x7fff702c5000 - 0x7fff702c5ff7 libsystem_blocks.dylib (74) <0D53847E-AF5F-3ACF-B51F-A15DEA4DEC58> /usr/lib/system/libsystem_blocks.dylib
0x7fff702c6000 - 0x7fff7034dfff libsystem_c.dylib (1353.100.2) <AF7873B0-AC4A-3C67-89BB-B8DA87718DAE> /usr/lib/system/libsystem_c.dylib
0x7fff7034e000 - 0x7fff70351ffb libsystem_configuration.dylib (1061.141.1) <0EE84C33-64FD-372B-974A-AF7A136F2068> /usr/lib/system/libsystem_configuration.dylib
0x7fff70352000 - 0x7fff70355fff libsystem_coreservices.dylib (114) <08B89E9B-C5B2-3E73-8964-03E58692B21F> /usr/lib/system/libsystem_coreservices.dylib
0x7fff70356000 - 0x7fff7035efff libsystem_darwin.dylib (1353.100.2) <BD5BAD5B-AC3F-371A-B4FC-ADF86D6DCE51> /usr/lib/system/libsystem_darwin.dylib
0x7fff7035f000 - 0x7fff70366fff libsystem_dnssd.dylib (1096.100.3) <01E0965B-83E5-356C-AC1F-C723F5AAB483> /usr/lib/system/libsystem_dnssd.dylib
0x7fff70367000 - 0x7fff70368ffb libsystem_featureflags.dylib (17) <6317641E-B43F-36A3-974E-6073786B94B9> /usr/lib/system/libsystem_featureflags.dylib
0x7fff70369000 - 0x7fff703b6ff7 libsystem_info.dylib (538) <4DD813CB-D7B0-3AB5-9054-D2E4FF7A64B9> /usr/lib/system/libsystem_info.dylib
0x7fff703b7000 - 0x7fff703e3ff7 libsystem_kernel.dylib (6153.141.1) <2B6311E6-6240-3EF7-8C87-475B66F7452C> /usr/lib/system/libsystem_kernel.dylib
0x7fff703e4000 - 0x7fff7042bfff libsystem_m.dylib (3178) <77A9D888-36E9-3968-8103-C82FFFC60B9E> /usr/lib/system/libsystem_m.dylib
0x7fff7042c000 - 0x7fff70453fff libsystem_malloc.dylib (283.100.6) <059F4DBD-856A-3A59-8B20-FD4B6918C5F2> /usr/lib/system/libsystem_malloc.dylib
0x7fff70454000 - 0x7fff70461ffb libsystem_networkextension.dylib (1095.140.2) <4CCE78C9-1DC4-3375-9828-D5BD739D23F3> /usr/lib/system/libsystem_networkextension.dylib
0x7fff70462000 - 0x7fff7046bff7 libsystem_notify.dylib (241.100.2) <DEAD75F2-DD34-3E8F-82DE-344625A2C25E> /usr/lib/system/libsystem_notify.dylib
0x7fff7046c000 - 0x7fff70474fef libsystem_platform.dylib (220.100.1) <97E825F6-D823-366C-9FF3-B1C8EA891044> /usr/lib/system/libsystem_platform.dylib
0x7fff70475000 - 0x7fff7047ffff libsystem_pthread.dylib (416.100.3) <80B053AA-B6F7-3B59-BC44-78A5A4F7368F> /usr/lib/system/libsystem_pthread.dylib
0x7fff70480000 - 0x7fff70484ff3 libsystem_sandbox.dylib (1217.140.4) <20BF94E2-DAB8-3EBE-AACE-99DF84C1C391> /usr/lib/system/libsystem_sandbox.dylib
0x7fff70485000 - 0x7fff70487fff libsystem_secinit.dylib (62.100.2) <28EDEB6F-899B-373D-B761-4C20D39285D9> /usr/lib/system/libsystem_secinit.dylib
0x7fff70488000 - 0x7fff7048fffb libsystem_symptoms.dylib (1238.120.1) <22800D8C-5C2A-3171-8C29-311BBE67F198> /usr/lib/system/libsystem_symptoms.dylib
0x7fff70490000 - 0x7fff704a6ff2 libsystem_trace.dylib (1147.120) <DC00C77E-4709-31F0-B913-CF09559B7A6F> /usr/lib/system/libsystem_trace.dylib
0x7fff704a8000 - 0x7fff704adff7 libunwind.dylib (35.4) <42B7B509-BAFE-365B-893A-72414C92F5BF> /usr/lib/system/libunwind.dylib
0x7fff704ae000 - 0x7fff704e3ffe libxpc.dylib (1738.140.1) <58E276A9-EE11-3F02-9D3E-5371E604E677> /usr/lib/system/libxpc.dylib
Sample analysis of process 92219 written to file /dev/stdout
jsynowiec
on 25 Aug 2020
@jsynowiec thanks for your report -- the next time this happens could you also upload a diagnostic? The logs will hopefully help us pin down the bit of code responsible.
Edited to add:
From the Sample of Docker:
Version: 2.0.0.3 (31259)
This is quite an old version-- there have been bugs fixed in this area recently. Could you try the latest edge version? https://desktop.docker.com/mac/edge/47376/Docker.dmg Thanks in advance!
djs55
on 25 Aug 2020
Im sorry to just shout here... but, for me at least, this new latest 47376 build (with gRPC-FUSE enabled) is not as good as the mutagen build. Mutagen build blew me away with speed and was stable.
Today I have fought with docker all day, deleting a vendor folder (1000s of files) takes forever, now Im getting read timeouts on the docker client and more... last night my Mac rebooted after a system fatal error (only thing different is docker version changed). For the first time in weeks Im hearing my Mac fans going full speed on a composer update...
I know Im ranting, without facts to back up and help, but I just want to register the fact its not all roses today :(
PhilETaylor
on 25 Aug 2020
@stephen-turner
My issues with high CPU due to serial console activity appear to still be resolved in this latest edge build.
nm777
on 26 Aug 2020
I had an horrible experience with Edge 2.3.5.0. There was no high cpu usage when no container is running, but the cpu usage goes through the roof once I start my container for a simple php web project, the login page takes minutes to load. It didn't make a difference if I had gRPC-FUSE turned on or not. Went back to Edge 2.3.4.0 for now
Diagnostics ID if you guys wanna have a look: 6DF43448-D8E6-475E-BC75-3613D91113E8/20200826150527
chnbz
on 26 Aug 2020
The new edge build works pretty well for me. I can work for quite some time comfortably. CPU use stays at around 25% with a couple of containers running.
But after a while (2 hours or so) or when waking my machine from sleep, com.docker.hyperkit flares up to 200% - 250% and stays there until I stop all containers. With no containers running I'm at 5% cpu.
vredeling
on 30 Aug 2020
Concur with @vredeling
Edge 2.3.6.0 is working much better for me. I think there is at least one dangling issue, however: Returning from sleep sends the hyperkit process spinning on all CPUs. Stopping the containers does not help. I am able to stop the bleeding be using Restart from the Docker tray icon. I have gRPC-FUSE enabled. Let me know if there is any information I can provide to help diagnose the issue.
JamesonNetworks
on 2 Sep 2020
With gRPC-FUSE enabled I'm getting some operation denied calls when a bazel build in the docker container attempts to create a symlink within a bind mounted directory.
jsharpe
on 3 Sep 2020
@vredeling @JamesonNetworks If you can reproduce this issue on waking the computer, please upload a diagnostics bundle and paste the GUID here. Thank you.
stephen-turner
on 7 Sep 2020
@jsharpe thanks for your feedback -- are you able to create and share a small repro case of the problem? If not, next time it manifests, could you upload a diagnostics report and quote the ID on a fresh ticket on https://github.com/docker/for-mac ? Thanks!
djs55
on 7 Sep 2020
@djs55 Yes to repro:
git clone https://github.com/abseil/abseil-cpp.git
cd abseil-cpp
docker run \
-e USER="$(id -u)" \
-u="$(id -u)" \
-v $PWD:/src/workspace \
-w /src/workspace \
l.gcr.io/google/bazel:2.2.0 \
--output_user_root=/src/workspace/build_output \
build //absl/...
Gives output when grpc-fuse is on:
Extracting Bazel installation...
FATAL: failed to create installation symlink '/src/workspace/build_output/a08c2e4811c846650b733c6fc815a920/install': (error: 1): Operation not permitted
When using osxfs you will see bazel build the software.
This is on edge 2.3.6.0
jsharpe
on 7 Sep 2020
@vredeling @JamesonNetworks If you can reproduce this issue on waking the computer, please upload a diagnostics bundle and paste the GUID here. Thank you.
@stephen-turner Alright, got an ID for the diag:
12F1947A-2753-47C1-A19E-A206946809E5/20200910125157
This is from version 2.3.6.0
Shutting down all of the containers seems to return the hyperkit process to normal. So this may be more a function of what I'm doing in containers (django services). However, I still do not believe returning from sleep should cause that kind of a meltdown, but at least the process does eventually calm down now.
After sitting with this issue for a couple of weeks, I'm noticing the high CPU calm down after about 30-40 mins. I assume this is actually expected behavior and not an issue. Wanted to come back here and update in case anyone was looking into it. I believe 2.3.7.0 solves all my CPU woes.
I appreciate all that the docker team is doing, thanks for the good work and awesome software everyone!
JamesonNetworks
on 10 Sep 2020
I just thought I'd report a positive outcome from upgrading to the 2.3.7.0 Edge release, following advice in the comments here.
For three days since upgrading from Stable 2.3.0.4 to 2.3.0.5, I had constant high CPU (and associated fan noise), despite virtually idle container activity.
Following the upgrade, I can report that hyperkit %CPU is sitting just under 20%:
j13k
on 23 Sep 2020
@vredeling @JamesonNetworks If you can reproduce this issue on waking the computer, please upload a diagnostics bundle and paste the GUID here. Thank you.
I've not encountered this issue any more since I moved to Docker Desktop 2.3.7.0
vredeling
on 25 Sep 2020
The latest CPU-related changes from the edge 2.3.7.0 have now made it to stable 2.4.0.0 for Mac and Windows. If you get a chance to try this, let us know how it goes. If there are still CPU problems please provide as much information as you can: ideally a repro example and a set of diagnostics.
Thanks for all your help so far!
djs55
on 30 Sep 2020
I just upgraded to 2.4 for Mac and CPU usage is a lot better for the app I'm running! The code is mounted inside the container during development and the app checks all relevant files (769 atm.) for changes every 5 seconds in order to auto reload. This usually caused a good spike in CPU usage up to around 50% CPU. Now there's a consistently low usage, mostly below 5%, when checking every second!
So I can confirm that IO performance and CPU usage have improved a lot in this update in my case.
Tested on: MacBook Pro (13-inch, 2017, 2,3 GHz Intel Core i5)
pkdetlefsen
on 1 Oct 2020
I'm still getting 2.3.7.0 as latest release, both on stable and edge channel. What's needed to get 2.4 to install?
andig
on 1 Oct 2020
@andig 2.4.0.0 is latest in Stable. 2.3.7.0 was never in Stable and never will be. See the Stable Release Notes for how to download any stable version. Note that you will lose all containers and volumes switching from edge to stable.
rfay
on 1 Oct 2020
I've upgraded to 2.4.0.0 and got a lot of ERROR: for <container-name> UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60) in our complex local dev stack, we instructed all devs to revert to the previous version which solved the issue (for now).
sdbruder
on 1 Oct 2020
I have updated Docker to 2.4.0 the CPU usage seems to be lower (now only around 10-12%) and everything has been running smooth so far on my MacBook Pro 2.8 GHz Quad-Core Intel Core i7.
aleks-rope
on 2 Oct 2020
Yes! this is a giant improvement!!!
Thanks everyone for working on this upgrade :confetti_ball: 🙏
KhaledMohamedP
on 5 Oct 2020
And even works on MacOS Big Sur ;-)
PhilETaylor
on 5 Oct 2020
hm the 2.4.0 build was behaving well so far without any fans running extensively all of a sudden without an apparent reason. but today after starting a project and leaving the computer for half an hour, just started up a project in DDEV right before, when i returned the fans were running on max and the cpu was spiking without a stop. :/
setup: macos 10.13.6 on a mbp 13" early 2011 8GB RAM with docker desktop 2.4.0 running a Drupal site with DDEV. i've sampled the .com.docker.backend process which was constantly at +/- 100% and com.docker.hyperkit which was around 10 to 30%... the samples:
samples.zip
p.s. and according to the deprecation notice for high sierra on the first startup of the minor 2.4.0 release it was the last release for macos 10.3 so no 2.4.x bug fix release anymore?
rpkoller
on 5 Oct 2020
Hey all,
We have now shipped the changes from our investigation over the last 3 months as part of the 2.4 Desktop release.
This does not mean we have got all of the bugs potentially causing this (we fixed a new one yesterday! ) but it is the point where we are no longer going to be driving a significant investigation into multiple potential root causes to this.
We will do a blog post in a few weeks detailing the things we found/changes we made to give you some insight into what we did and why.
If you are still having issues, I would ask that you create new tickets on for-mac rather than comment on old tickets as we are going to close these to keep our backlog a bit tidier and not mix up the messages (and it is easier for us to get signal on the scale of issues this way).
Thanks again for your patience and an even bigger thank you to all of you who took the time to test builds & upload diagnostics!
nebuk89
on 8 Oct 2020
@nebuk89 can you share link to blog post if it was written?
sashaaKr
on 12 Apr 2021
@sashaaKr Unfortunately we never got round to writing the blog post.
stephen-turner
on 12 Apr 2021
Related issues
rfay
·
3Comments
esemate
·
4Comments
BretFisher
·
3Comments
iben12
·
6Comments
ollypom
·
5Comments
Most helpful comment
We've managed to repro one source of unexpected high CPU in
hyperkitandcom.docker.osxfsbydocker run -v ~/vscode:/anywhere alpine shyarn installThe build generates a lot of file events which are all injected into the VM.
Unfortunately there are so many file events generated, it takes a long time for them to be fully processed. The build finishes quickly but
hyperkitandcom.docker.osxfsremain busy for a very long time.We have an experimental prototype build which we believe fixes this particular problem, if you'd like to try it. The build is based on Edge and can be downloaded from https://desktop-stage.docker.com/mac/edge/46421/Docker.dmg . The build does 3 things to improve performance:
If you have a chance to try it, let us know what happens! Note that this is an experimental build and won't work with existing containers -- they will need to be re-created. It might be necessary to reset to factory defaults before and after using this build.