That worked, thank you!

Yes, it's still happening on 14.1b1 and b2. Every time the screensaver is activated, I can see an additional thread being created in the legacyScreenSaver (Wallpaper) process. The closest I have to a workaround is to poll the view's window's windowLevel, which appears to change depending on whether the screensaver is currently active. One thought I had was that there was some kind of retain cycle happening, and that's why my view isn't getting deallocated in this new screensaver process, but it doesn't seem to be the case at least when it's running within a regular app context. Also, I do get the "startAnimating" calls, but never see any "stopAnimating" calls.