mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-10-24 09:46:59 -06:00
dotCooCoo
4821ec92c2
Within about a minute of its window no longer being visible, macOS App Nap lowers the app's threads to the lowest priority and coalesces its timers. On a loaded machine, control requests then took seconds to answer, and the 60 s timeout reply arrived up to 26 s late. When the control channel is on (--control or VECTORCRAFT_CONTROL_PORT), the app now holds an NSProcessInfo activity (user initiated, allowing idle system sleep, latency critical) for as long as it runs, so App Nap does not apply. The activity does not keep the Mac awake. docs/control-protocol.md states this in the paragraph on the 60 s timeout.