Googling indicates that it's part of this software.
ahhhh. thank you. man, I got nothing from teh googles... even when I add Dill to the mix.
oh well. thank you again.
We use Dill here, and ran into this issue when students launched secure browsers as a part of standardized testing.
Reach out to your Dill support channel, they have two items that should help:
1. Pre-release version of Dill that adjusts the way the culprit launchdaemon/process works - this should resolve secure browser conflicts. v1.8.2.16 as of 10/17/2017.
2. Terminal command to unload the rescuerecordings launchdaemon - run as sudo if running locally (will need to reload prior to Dill use):
launchctl unload /Library/LaunchDaemons/com.swifteducationsystems.rescuerecordings.plist
Cheers!
Edit: should be noted that option 2 is not necessary if you've gone the upgrade option 1 route