Aerial
Aerial copied to clipboard
JohnCoates
Screensaver hangs after ~15 minutes (i.e. no movement, seconds do not move, display never turns off)
General troubleshooting tips
Before logging an issue please check that:
- [x] You have the latest version installed (There may be a beta version that fixes your issue), see here for the latest releases and bug fixes: https://github.com/JohnCoates/Aerial/releases
- [x] Your issue isn't already mentioned in our issues. You may find a workaround there or a similar request already made.
- [x] Your problem isn't mentioned in the troubleshooting page.
If none of this fixes your issue, tell us about the problem you are experiencing or the feature you'd like to request.
Required information
In order to help us sort your issue, we ask that you provide the following information:
- [x] Mac model: M1 Mac Mini (16Gb)
- [x] macOS version: 12.2 (21D49)
- [x] Monitor setup: 1x (external) 32" 4k ThinkVision (LG). Using USB-C to DP (via a KVM switch).
If appropriate, please enable Debug mode and Log to disk in Advanced tab and replicate your bug, then attach the AerialLog.txt file (You can access this file through the Advanced tab).
Description of issue / Feature request
- Several times a day the screensaver will hang (i.e. video stops moving, monitor does not turn off, video stuck with date time not changing).
- (past few months it was once or twice a week, now it's very common -- this has been going on for months)
- This seems to happen after 15 or so minutes (i.e. when the monitor is supposed to turn off/go black)
- This does not reliably happen. I had a previous M1 Mac Mini (same monitor setup) that (I think) would not have this problem (I have since returned the Mac Mini to my employer, so can't test anymore). I can't seem to replicate this on my Intel Macbook Pro and my two M1 Pro Macbook Pro (no monitor) -- videos play properly and after the delay, the monitor properly turns off.
- I'm using little snitch (on all devices) but all outgoing connections are allowed
Hey @Tuinslak
I'll have a look at your log later today but in general, Aerial is killed by macOS (it can't stop on itself). Screensavers are a bit powerless, macOS is in charge of everything in general when it comes to starting, stopping, killing or putting your screen to sleep.
Note that there are many related issues to going to sleep currently in Monterey, the latest being this one : https://9to5mac.com/2022/02/08/macos-12-3-beta-2-addresses-bluetooth-related-battery-drain-on-macbooks/
Some of those bugs have been going on since the release of Monterey and may be part of what's happenning to you here. I'll have a look and try to give you a better answer but those are usually macOS issues in general.
Thanks.
This has been going from before Monterey (but I assume some of the Apple bugs have been around for a while... :) ).
Another thing is that is does not actually hang the whole computer: any input (mouse/keyboard) stops the screensaver and heads back to the login page. After ~5 minutes the screensaver will start again and may or may not hang after a while.
How it works change all the time but usually...
- You login (or macOS decides to go to sleep for good)
- macOS tells us it will stop the screensaver <- at that point, I stop the video and the overlays, so that could explain what you see as "stuck"
- macOS may or may not call the proper api to stop us (which is why I do the thing above)
- your screen goes to sleep or macOS comes back to the desktop
- mayyyyybe 8/9 seconds later, macOS kills our parent app extension (made by apple) and that kills the screensaver
That's part of the reason why I pause everything, because if not your mac would keep playing aerial in the background, Aerial thinking that it should still run. It's a whole mess !
Heh, sounds like a mess -- but indeed looks like it could be that the video gets stopped but OSX doesn't actually turn off the display for some reason.
This isn't always helpful but try this :
pmset -g log |grep "Wake Request"
Sometimes it will tell you exactly why it doesn't go to sleep, although it's not always the case.
I see a lot of UserRequestedBackup (TimeMachine?).
Log: wake.txt -- Is there anything useful in there?
I had a very very quick look and it's hard to say, nothing pops particularly. I suggest next time you see it hanging, note the time it happen and check the log again.
The bluetooth sleep issue doesn't show in that log, so it's a bit of a hit and miss.
I've been testing with a default screensaver (flurry) and everything works fine there. Let me try Aerial back and see what happens
Hey again, did you update to 12.2.1 yet ? They fixed some fairly important sleep bugs that may have been related : https://9to5mac.com/2022/02/10/apple-releases-macos-12-2-1-with-bluetooth-battery-drain-fix/
Yeah -- I did. It hung again just now. I'll check when it hangs based on the time + see if there's anything in the log next time it happens (I keep needing to use my Mac and then forget at what time the screensaver hung). I'll let you know.
Something I noticed, hitting Apple logo (top left) -> sleep fails quite often.
It turns off the monitor for about a second or two and then turns it back on, even though there's no mouse/keyboard input/movement...
I need to do it several times for the Mac to properly go to sleep and the monitor to turn off, or use this script: alias macsleep="pmset sleepnow"...
But then I'd expect it to fail on the default screensavers too. Not only on Aerial. Meh...
Well, not all screensavers are equal in the sense than there are basically 3 different paths to take for macOS to launch one. All third party screensavers run from something called legacyScreenSaver.appex but that's not true of all nor most of the Apple ones.
The fact that sleeps fail is very weird though, I'll think about it a bit and get back to you.
Okay -- so this is what it looks like when it hangs:
Stuck at the time:
And then the log:
cut and paste:
2022-02-17 12:48:55.886 : string : 12:48:55
2022-02-17 12:48:55.890 : string : Thursday, February 17
2022-02-17 12:48:56.887 : string : 12:48:56
2022-02-17 12:48:56.890 : string : Thursday, February 17
2022-02-17 12:48:57.887 : string : 12:48:57
2022-02-17 12:48:57.890 : string : Thursday, February 17
2022-02-17 12:48:58.887 : string : 12:48:58
2022-02-17 12:48:58.890 : string : Thursday, February 17
2022-02-17 12:48:58.944 : string : Moving toward Tuolumne Meadows in
Yosemite National Park, United States
2022-02-17 12:48:59.887 : string : 12:48:59
2022-02-17 12:48:59.890 : string : Thursday, February 17
2022-02-17 12:49:00.887 : string : 12:49:00
2022-02-17 12:49:00.890 : string : Thursday, February 17
2022-02-17 12:49:01.887 : string : 12:49:01
2022-02-17 12:49:01.890 : string : Thursday, February 17
2022-02-17 12:49:02.887 : string : 12:49:02
2022-02-17 12:49:02.890 : string : Thursday, February 17
2022-02-17 12:49:03.888 : string : 12:49:03
2022-02-17 12:49:03.892 : string : Thursday, February 17
2022-02-17 12:49:04.886 : string : 12:49:04
2022-02-17 12:49:04.890 : string : Thursday, February 17
2022-02-17 12:49:05.887 : string : 12:49:05
2022-02-17 12:49:05.891 : string : Thursday, February 17
2022-02-17 12:49:06.888 : string : 12:49:06
2022-02-17 12:49:06.893 : string : Thursday, February 17
2022-02-17 12:49:07.887 : string : 12:49:07
2022-02-17 12:49:07.891 : string : Thursday, February 17
2022-02-17 12:49:08.888 : string : 12:49:08
2022-02-17 12:49:08.892 : string : Thursday, February 17
2022-02-17 12:49:09.887 : string : 12:49:09
2022-02-17 12:49:09.891 : string : Thursday, February 17
2022-02-17 12:49:10.570 : ############ willStop
2022-02-17 12:49:10.572 : <AerialView: 0x12de52a80> stopAnimation
2022-02-17 12:49:10.573 : <AerialView: 0x12de52a80> observeValue Optional("readyForDisplay") false
2022-02-17 12:49:10.585 : ############ willStop
2022-02-17 12:49:10.585 : <AerialView: 0x13aa55f70> stopAnimation
2022-02-17 12:49:10.586 : ############ willStop
2022-02-17 12:49:10.586 : <AerialView: 0x13aa55f70> stopAnimation
2022-02-17 12:55:25.986 : avInit .saver (0.0, 0.0, 296.0, 184.0) p: true o: true
2022-02-17 12:55:25.987 : Best match appearance : Optional(__C.NSAppearanceName(_rawValue: NSAppearanceNameAqua))
2022-02-17 12:55:25.987 : Effective Appearence : <NSCompositeAppearance: 0x130908880>
2022-02-17 12:55:25.987 : Time Management initialized
2022-02-17 12:55:25.987 : Starting Location initialization
2022-02-17 12:55:25.987 : Location services enabled
Around 12h55 I unlocked my Mac again.
Hey @Tuinslak
Thanks for your patience and follow up on this.
So basically, we're being told that macOS is going to kill us, so at that moment I pause the video preventively. And nothing happens on top of that, we don't get killed it seems.
I have a hard time figuring out why, just to be clear, Aerial can't quit on its own. The fact that you said
"Something I noticed, hitting Apple logo (top left) -> sleep fails quite often."
Leads me to think that you probably have something that prevents your mac going to sleep.
At this point I'd probably try resetting PRAM and NVRAM if you can ?
Make sure you’re not running Caffeine or Amphetamine. Aerial was hanging for me until I stopped a caffeinate command that was running in a terminal tab.
Hey --
Not running Caffeine or Amphetamine.
As this is a M1 I understand clearning pram/nvram is no longer really possible. At least no shortcuts at boot.
However I ran:
$ sudo nvram -c
nvram: Error clearing firmware variable fmm-mobileme-token-FMM: (iokit/common) not permitted
nvram: Error clearing firmware variable fmm-mobileme-token-FMM-BridgeHasAccount: (iokit/common) not permitted
nvram: Error clearing firmware variable fmm-computer-name: (iokit/common) not permitted
And did an SMC reset by pulling the power cable for 30+ seconds, and then plugging it back in.
And rebooted... let's see if that does anything at all.
@Tuinslak
Ok this is going to be a bit of a weird idea, but could you go into Aerial's settings, press Advanced, scroll down and uncheck "Debug mode" ?
I'm wondering if the logging stuff isn't causing issues in the latest Monterey...
Dear all,
Just jumping in to say I have exactly the same issue, with a similar setup and Aerial 3.0.6.
Mac model: M1 Mac Mini (16GB) macOS version: 12.1 (21C52) Monitor setup: 1x (external) 32" 4k BenQ PD3220U display (HDMI)
Like @Tuinslak the screensaver freezes randomly, but rather frequently recently. The log contains the same key messages:
2022-03-13 15:36:50.412 : ############ willStop
2022-03-13 15:36:50.414 : <AerialView: 0x125773a60> stopAnimation
2022-03-13 15:36:50.414 : <AerialView: 0x125773a60> observeValue Optional("readyForDisplay") false
2022-03-13 15:36:50.416 : ############ willStop
2022-03-13 15:36:50.417 : <AerialView: 0x125773a60> stopAnimation
2022-03-13 15:36:50.417 : ############ willStop
2022-03-13 15:36:50.418 : <AerialView: 0x125773a60> stopAnimation
2022-03-13 15:36:50.418 : ############ willStop
Symptoms are the same as described above: video stops moving, monitor does not turn off, video stuck with date time not changing. At the time where the screensaver outputs the 'willStop' debug message, something can be seen in the output of pmset, but I have absolutely no idea how to interpret it.
2022-03-13 15:36:40 +0100 Assertions PID 159(WindowServer) TimedOut UserIsActive "com.apple.iohideventsystem.queue.tickle serviceID:1005ce8b2 name:AppleUserHIDEventSe product:USB Receiver eventType:17" 00:59:59 id:0x0x90000a29a [System: PrevIdle DeclUser kDisp]
2022-03-13 15:36:40 +0100 Assertions Summary- [System: PrevIdle] Using Batt
2022-03-13 15:36:50 +0100 Notification Display is turned off
2022-03-13 15:36:50 +0100 Assertions PID 102(powerd) Released PreventUserIdleSystemSleep "Powerd - Prevent sleep while display is on" 01:43:57 id:0x0x10000a29b [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 102(powerd) Summary ExternalMedia "com.apple.powermanagement.externalmediamounted" 893:57:02 id:0x0x800008dc4 [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 57852(mdsync) Summary BackgroundTask "com.apple.metadata.mds.scan" 00:52:01 id:0x0xb0000a462 [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 211(coreaudiod) Released PreventUserIdleDisplaySleep "com.apple.audio.context24250.preventuseridledisplaysleep" 00:40:09 id:0x0x50000a4a8 [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 211(coreaudiod) Released PreventUserIdleSystemSleep "com.apple.audio.context24250.preventuseridlesleep" 00:40:09 id:0x0x10000a4a7 [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 211(coreaudiod) Released PreventUserIdleDisplaySleep "com.apple.audio.context24251.preventuseridledisplaysleep" 00:40:09 id:0x0x50000a4ac [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 211(coreaudiod) Released PreventUserIdleSystemSleep "com.apple.audio.context24251.preventuseridlesleep" 00:40:09 id:0x0x10000a4ab [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 211(coreaudiod) Released PreventUserIdleDisplaySleep "com.apple.audio.context24252.preventuseridledisplaysleep" 00:40:09 id:0x0x50000a4b0 [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 211(coreaudiod) Released PreventUserIdleSystemSleep "com.apple.audio.context24252.preventuseridlesleep" 00:40:09 id:0x0x10000a4af [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 211(coreaudiod) Released PreventUserIdleDisplaySleep "com.apple.audio.context24253.preventuseridledisplaysleep" 00:40:09 id:0x0x50000a4b4 [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 211(coreaudiod) Released PreventUserIdleSystemSleep "com.apple.audio.context24253.preventuseridlesleep" 00:40:09 id:0x0x10000a4b3 [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 154(AirPlayXPCHelper) Released PreventUserIdleSystemSleep "com.apple.airplay.APAudioEngineBuffered.timed" 00:40:09 id:0x0x10000a4a4 [System: No Assertions]
2022-03-13 15:36:50 +0100 Assertions PID 154(AirPlayXPCHelper) Released PreventUserIdleSystemSleep "com.apple.airplay.APAudioEngineBuffered.counted" 00:40:09 id:0x0x10000a4a3 [System: No Assertions]
One last piece of info: it seems that that the image freezes at exactly 10 seconds after the time where the display should in fact turn off. My settings are to keep the screensaver on 40 minutes (turn on aerial after 20 minutes, turn off screen after one hour), and the 'bug' is seen in the log 40 minutes after the initial message indicating that the screensaver session had started:
2022-03-13 14:56:40.886 : avInit .saver (0.0, 0.0, 2560.0, 1440.0) p: false o: false
Hope this can help pinpointing the cause of the issue, even if from what I read above it seems to be more a macOS problem.
Thanks for the report @chucklapuck
I'm finally getting a M1 based mac, hopefully by the end of the coming week, so hopefully I can reproduce the issue. I'll keep everyone posted, thanks for your patience on this.
@glouel and others on this thread,
For what it is worth, I am running v3.0.6 of Aerial on a 2020 MBA M1. I just updated to the latest Monterey MacOS 12.3 (21E230). Also, my power adapter setting is set to turn the display off after 2 hours. I have not seen any "freezing" behavior.
Yes -- FWIW on my two M1 MacBook Pro (14") devices, the screensaver never hangs. It's only on the M1 Mini.
Let me know if the bug still occurs in macOS 12.3 after you upgrade, I hope they might have fixed some stuff in there, as there were some sleeping bugs in previous Monterey versions.
Well, thanks for the report in any case. I'll try to get back to all of you this week end, and see if I can dig around more into it.
Well, I finally have an Apple Silicon mac and there seems to be many bugs surrounding sleep that may be related to what you experienced (and overall, so many random bugs !). One thing I noticed is my Mac waking itself up every few minutes at night for a while, something that randomly stopped after a few days. It's something that was also reported to me.
I haven't seen the not going to sleep issue with Aerial though, but while digging into sleep issues, I found out this particular report : https://github.com/MonitorControl/MonitorControl/issues/973
And this got me thinking, bit of a long shot but who knows, can you check if you have the brightness dimming enabled in Aerial's settings ? And if so try disabling it ?
It's more likely to be a coincidence and just some macOS bug but who knows. I'm hopeful we'll get a new macOS beta soonish.
Thanks for the suggestion. I had a look and brightness dimming (lower brightness when playing videos) was already disabled on my machine -- yet the bug still occurs.
Hi Folks, I’m reading about your issues here. Fyi….on a 2020 M1 MBA running the latest versions of Arial (v3.0.6) and MacOS (v12.3 — 21E230), I’ve not experienced any “freezing” of the Ariel videos or the clock widget. I almost always keep my machine plugged in and do tweak the brightness controls; the display is set to sleep after an hour.
We're talking about this option right?
Let me disable it, but if that didn't work for @chucklapuck I'm sceptical... :)
Hey everyone
So I have a temporary workaround, this is not great, but it should make things less worse : https://github.com/JohnCoates/Aerial/releases/tag/v3.0.8beta1
What that build does is, when Aerial is told to stop, I now clear the video and the overlays, so you should not have a frozen anything hopefully, but a black screen. This may still not let your mac properly go to sleep, but it should be less worse.
Please let me know if you see an improvement or not.
The problem I have is that aerial will stop after playing the first video, like a picture, and won't jump to the next video. The above text comes from Chinese translation.
I am on 12.3.1 as of this morning and I can report that the issue is still occurring unfortunately.
I hesitate to jump in here, but this additional context may be helpful to your discussions: I do not use Aerial, but have been having the same problem described by OP over the last 4 months or so with MacOS native screensavers - basically since updating to Monterey. This is on two different Macs - an M1 Air and an M1 Pro 14" MBP, and only when using an external display. I do use Amphetamine (mentioned by @carlosfoster above) while docked, although quitting it seems to have no effect. There is also a thread over on Reddit, although it is not helpful. I have found some relief by attaching my external monitor directly rather than through my Thunderbolt dock (a CalDigit Elements Hub), although it is not a solution.
@alexclaydon thanks a lot for taking the time to post this, that's actually super helpful. I had a strong hunch that it was on Apple but with no data on other screensavers it's always hard to figure out.
The bit about the external monitor is interesting and could explain why most people see the issue on minis it seems. Apple supposedly fixed some bugs with 12.3.1 but in my case they made it worse. While I never managed to reproduce the issue, I have 2 displays on my M1 mac (1 apple, 1 basic 4K monitor) and with latest update I've seen random disconnection of the 4K one, and weirdly enough came back to my mac with my main display switched from the 5K to the 4K 😅
Prior to update, while asleep (without the freezing) the 4K monitor would randomly wake up and turn off.
Seeing the freezing bug happen on Drift, I think it explains why my latest counter measures didn't work in the beta, it just freezes before I can do anything.
Let's hope for a prompt resolution, I would very much suggest all of you who have the bug to file a feedback in Apple's feedback assistant. It can seem like throwing something into the void but on things like this, it definitely helps. Feel free to link this thread and the reddit one.
Edit : Also some more info about your exact monitor configuration in this thread may help others, though I'm not sure there's more I can do on that one.
Just to contribute with some specs, if these are at all helpful. I'm getting the same hanging issued described above. I'm on a M1 max MBP 16". it's almost always docked through CalDigit TS3+ (thunderbolt only) to a LG 43 4K monitor. I didn't notice this happening on my previous MBP that was an intel 15" (also Monterey). So I don't know that it's OS related, but could be M1 related. Tried an uninstall and fresh install to current release and beta versions. Results are the same.
@glouel & others here, FWIW...3rd post here in the last month about not being able to reproduce this issue. I'm running a pretty vanilla 2020 M1 MBA and never use an external monitor (but I do occaisionaly use Monterey's Universal Control or also the same iPad as an extended monitor). I just upgraded to 12.4 Beta (21F5048e) and I have Aerial 3.0.8beta2 installed. It is mostly always used plugged into the Apple power brick.
I have been forcing the screensaver to kick-in a lot this week to see if I could get it to freeze like others are experiencing and I'm just not seeing it.
Good luck on this...let me know if you want me to try anything.
Update....the internal display settings on my MBA are set to the highest native resolution of the panel--1680x1050.
I wonder if there is any pattern around external monitors? My Mac mini M1 has an LG monitor plugged in via HDMI.
On Fri, 8 Apr 2022 at 12:29, Pcar17 @.***> wrote:
@glouel https://github.com/glouel & others here, FWIW...3rd post here in the last month about not being able to reproduce this issue. I'm running a pretty vanilla 2020 M1 MBA and never use an external monitor (but I do occaisionaly use Monterey's Universal Control or also the same iPad as an extended monitor). I just upgraded to 12.4 Beta (21F5048e) and I have 3.0.8beta2 installed. It is mostly always used plugged into the power supply.
I have been forcing the screensaver to kick-in a lot this week to see if I could get it to freeze like others are experiencing and I'm just not seeing it.
— Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/1225#issuecomment-1092382293, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF5Q54Y2C4U5LQMNMYZ6W5DVD6KYFANCNFSM5N4GR7OQ . You are receiving this because you commented.Message ID: @.***>
-- Jason Pearse
http://jpcanfixit.com.au http://jpcanfixit.com.au/
0414 534 551
- http://jpcanfixit.com.au/*Computer and technology repairs, advice and training, on-site and remote
Yes, I'm starting to think it's related to external monitors.
System Information:
Apple M1:
Chipset Model: Apple M1
Type: GPU
Bus: Built-In
Total Number of Cores: 8
Vendor: Apple (0x106b)
Metal Family: Supported, Metal GPUFamily Apple 7
Displays:
LEN P32p-20:
Resolution: 6016 x 3384
UI Looks like: 3008 x 1692 @ 60.00Hz
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Tons of issues surrounding sleep with an external monitor so you may just be one of the unfortunate ones. See this reddit thread for some general background : https://old.reddit.com/r/macmini/comments/r8akul/screensaver_freezing_bug/
and another one on people with kind of similar issues here (though not exactly the same) : https://github.com/JohnCoates/Aerial/issues/1225
It's pretty much always a M1 based mac + a non-apple external display acting up. 12.3.1 fixed some bugs but made some stuff worse too. Although it doesn't seem to affect everyone or everyone the same way.
I switched recently to a Mac studio + Studio display and that setup works fine, although as soon as I plug an additional 4K monitor, I get weird sleep stuff (waking up from sleep then going back to sleep). It's a bit of a mess :(
I wasn't sure in the Feedback app (to Apple) which category to choose, so have filed it under Sleep/Wake issues. Hopefully they will spot it and sort it out.
On Sun, 10 Apr 2022 at 02:31, Guillaume Louel @.***> wrote:
Tons of issues surrounding sleep with an external monitor so you may just be one of the unfortunate ones. See this reddit thread for some general background : https://old.reddit.com/r/macmini/comments/r8akul/screensaver_freezing_bug/
and another one on people with kind of similar issues here (though not exactly the same) : #1225 https://github.com/JohnCoates/Aerial/issues/1225
It's pretty much always a M1 based mac + a non-apple external display acting up. 12.3.1 fixed some bugs but made some stuff worse too. Although it doesn't seem to affect everyone or everyone the same way.
I switched recently to a Mac studio + Studio display and that setup works fine, although as soon as I plug an additional 4K monitor, I get weird sleep stuff (waking up from sleep then going back to sleep). It's a bit of a mess :(
— Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/1225#issuecomment-1094080023, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF5Q542SAMGN5RWFKB4NAFDVEGWHRANCNFSM5N4GR7OQ . You are receiving this because you commented.Message ID: @.***>
-- Jason Pearse
http://jpcanfixit.com.au http://jpcanfixit.com.au/
0414 534 551
- http://jpcanfixit.com.au/*Computer and technology repairs, advice and training, on-site and remote
On the latest Monterey 12.4 beta (21F5071b), this problem appears to have been sorted out. Perhaps Apple have stopped killing the screensaver behind the scenes? I'll keep testing, have only just tried it once today.
Oh, that would be great. Please keep up posted @baobab68 !
I'm also running the beta and the side issue I have (secondary monitor briefly waking up and shutting down again after your mac went to sleep, screensaver or not) haven't been fixed but let' s hope they fix this important one.
Seems like it's working fine now. I set my screen to sleep after 60 mins and Aerial for 10 mins and the screen saver's clock was still running 45 mins later and the screen then went to sleep as expected. 🤞🏻 it might be fixed!