4 ms·
The thread focuses on the problematic code, not the performance impact it has. The second (collapsed) __CFRunLoopRun in the sample screenshot contains all the r
by saagarjha 6y ago
The thread focuses on the problematic code, not the performance impact it has. The second (collapsed) __CFRunLoopRun in the sample screenshot contains all the resultant drawing happening in-process, with which Finder used about 20% of the CPU. WindowServer was using about ~25% to keep up.