3 ms·
Don't know, but if you want to find out, `sudo spindump -onlyTarget coreaudiod` is a good starting point. You can also try `log stream --process coreaudiod --i
by comex 4y ago
Don't know, but if you want to find out, `sudo spindump -onlyTarget coreaudiod` is a good starting point. You can also try `log stream --process coreaudiod --info --debug` to see if it's logging anything.
- viraptor 4y agoAnother tool to dig deeper is dtrace. There's a few articles about using it.
- lunixbochs 4y agoI've had luck using Instruments whole system profiling to debug this kind of system process
- antonmladenov 4y agothe second command logs out nothing. the first one produces a super long txt file with logs which I absolutely do not understand.