[quote='878094022, WangZiYuan, /thread/817264?answerId=878094022#878094022, /profile/WangZiYuan'] I’m not quite sure what you mean by the 'sysex process.' [/quote] OK, lemme clarify. On macOS, content filters must be packaged as a system extension [1], aka a sysex. A sysex is much like a launchd daemon, in that it can potentially run for the entire boot cycle, that is, start when you boot the Mac and not stop until you shut down [2]. Your Network Extension provider instances are created within that sysex process. So, consider this sequence: You boot your Mac. Your sysex starts. NE instantiates your content file provider within that sysex process. You stop the filter. NE stops the content filter provider. At this point the system may or may not stop your sysex process. But let’s consider what happens if it doesn’t… You start the filter again. NE instantiates your content file provider again, still within the same sysex process. So, my questions are: Are you seeing the sysex process stop at step 6? If not, if y
Topic:
App & System Services
SubTopic:
Networking
Tags: