site_archiver@lists.apple.com Delivered-To: cocoa-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-bremen.de; s=2019; t=1744721888; i=@uni-bremen.de; bh=X6hp1vFz3EjtyxeLeiuNPd6lv42bElgjR2U3gIWRTkI=; h=From:Subject:Date:References:To:In-Reply-To; b=IZZNefpO94K+MYyHhBEITwPO1uXz0puXGKuVi4Q89xkfDeIW/fNbyJLT9I+Anm3B7 rVBWXAIZbGogB6TQY5orCsqjQWnJMt/ERn62RsL00GGQOQ++FmR1XVeWMRA6YQ/zxj CiKRXgOmlFz0xQsv0hIhkRFiBLG7bk2lyBdo795oueDFF/vXhsW02J85z9doEqI5Ye 6PLIBzfJ2+eBsmu3Hi92ZOO7DsInr5uFXqJgeYgv1FrvrMtGdBZ/B3wwqrknhs7Qls MxHYDe0ghnjROvm1scVQPXA7M7REdigsjSt2dvUNogGHNyUOK+fhrTENde2GaYPfoR 7MY11aWTXQxFQ==

No, that's not what I mean. You won't see multiple legacyScreenSaver processes, but you should note that each time you start and stop your screensaver, you should see the memory and cpu (depending on how much

I see, yes that seems to be the case , at least for the memory part. Over time, the process uses over 2 GB. (No CPU, though)

Using something like those XXXXXXXXXXX will make it easier to filter them in Console.app. You should see the starts, but not the stops.

Right. I think I noticed that, too. But that does not explain, why new settings will not become persistent, does it? I mean, when I do [defaults_ setObject: monitor_user_prefs forKey: displayName_]; the Mac *could* write the new settings into persistent memory/disk ... Or is there a dedicated command that would force macOS to write the settings? There is the -synchronize method, but the docs say it's not necessary any more.

because legacyScreenSaver is just weird.

That whole business brings up the question: should we abandon legacyScreenSaver? If I understand correctly, there is a new framework, something to do with wallpapers? I mean, the name "legacyScreenSaver" suggest, that this framework will be going away anyways at some point ... What are your thoughts? Best regards, Gabriel _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com smime.p7s