User Profile

Hey @eskimo or anybody who can help, we are on 14.0 beta 7 and screensaver bugs with Sonoma are still happening. In this case the bug shows up one or more monitors, for screensavers that use WKWebView internally. The WKWebView will render HTML and JavaScript, but only partially: video tags don't play unless you goose them with a hack JavaScript SetAnimationFrame() fails JavaScript SetInterval() only fires about once per second These issues affect many third-party screensavers which internally use a HTML/CSS/Javascipt engine. reported as FB13094564 There are a bunch of other legacyScreenSaver issues with Sonoma that aren't WebKit-related as well, but most of those we have been able to find workarounds for. Thanks!

Hey @eskmio or anybody who can help, we are on 13.3 RC and this multimonitor screensaver bug is still happening. It's affecting most (but not all) screensavers when run on a 2+ monitor system. Relevant discussions: https://forums.macrumors.com/threads/macos-13-3-rc-bug-fixes-changes-and-more.2384357/post-32056536 https://forums.macrumors.com/threads/multimonitor-screensaver-bug-in-ventura-13-3.2384444/ https://iscreensaver.com/forum/discussion/568/ventura-13-3-beta-bug-with-multimonitor-screensavers https://github.com/JohnCoates/Aerial/issues/1286

Ventura 13.3 beta 2 seems to have a big problem with screensavers on multimonitor system. This affects some first-party Apple screensavers, and several third-party screensavers. Reported as FB12023530 To reproduce: on a M1 MacBook Air with a second monitor connected open System Preferences / Screen Saver and select the Message Screen Saver click the Preview button Expected behavior: screen saver should run on both monitors Actual behavior: screen saver runs on 2nd monitor only. Actual behavior: the screen’s rectangle seems to be offset by about 100 pixels (as if the NSView is not set to the actual screen coordinates) Regression: this worked fine in 13.2 this also affects third party screensavers such as iScreensaver and Aerial this doesn’t affect all first party Apple screensavers, e.g. “Hello” and “Flurry” work fine, but “Message” does not

In Beta 2 of Ventura 13.1 (22C5044e) I'm seeing consistent WebKit crashes: Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BREAKPOINT (SIGKILL) Exception Codes: 0x0000000000000001, 0x00000001aebfe8d0 Termination Reason: Namespace PAC_EXCEPTION, Code 1 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 JavaScriptCore 0x1aebfe8d0 WTFCrashWithInfoImpl(int, char const*, char const*, int, unsigned long long) + 4 1 WebKit 0x1b53971dc WebKit::AuxiliaryProcess::didReceiveInvalidMessage(IPC::Connection&, IPC::MessageName) + 612 2 WebKit 0x1b55b4b74 IPC::Connection::dispatchMessage(std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >) + 1424 3 WebKit 0x1b55b750c ***::Detail::CallableWrapper<IPC::Connection::enqueueIncomingMessage(std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >)::$_13, void>::call() + 188 4 JavaScriptCore 0x1aec3fb90 ***::RunLoop::performWork() + 200 5 JavaScriptCore 0x1aec408c8 ***::RunLoop::performWork(void*) + 36 6 CoreFoundation 0x195493a18 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 7 CoreFoundation 0x1954939ac __CFRunLoopDoSource0 + 176 8 CoreFoundation 0x19549371c __CFRunLoopDoSources0 + 244 9 CoreFoundation 0x195492320 __CFRunLoopRun + 836 10 CoreFoundation 0x195491888 CFRunLoopRunSpecific + 612 11 Foundation 0x196399e58 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212 12 Foundation 0x196412cf0 -[NSRunLoop(NSRunLoop) run] + 64 13 libxpc.dylib 0x19512f380 _xpc_objc_main + 860 14 libxpc.dylib 0x19512eca0 xpc_main + 108 15 WebKit 0x1b53c69ec WebKit::XPCServiceMain(int, char const**) + 256 16 dyld 0x19508be50 start + 2544 This is happening in an x64 app which is using WKWebView, running on a M1 mac. I'm not sure what is causing this, but I suspect it may have something to do with using the JavaScript function: webkit.messageHandlers.javascriptToHost.postMessage(); Submitted as FB11786440 Anyone else seeing this?

Starting in Monterey 12.1 (Intel), our custom 3rd party screen saver is occasionally failing to work properly when in the Preview mode (e.g. the small sample window inside the Desktop & Screen Saver system preferences window). If I turn on detailed logging, I see the following calls being made: ScreenSaverView.Init ScreenSaverView.hasConfigureSheet ScreenSaverView.draw However, ScreenSaverView.StartAnimation ScreenSaverView.AnimateOneFrame are never called Oddly, this only happens when first opening the Desktop & Screen Saver window. Because, if you: start the screensaver (using the Preview button or a Hot Corner) then exit the screensaver open the Screen Saver Options panel for this screensver then close it switch to another screensaver then back... Any of these actions will cause the screensaver preview to start working. This sounds a little bit like what's beeing seen in https://github.com/JohnCoates/Aerial/issues/1190 which is a different 3rd party screensaver.

Starting with Catalina Developer Beta 5, third-party screensavers are no longer able to receive and respond to keyboard and mouse events. Many third-party screensavers make use of this feature. The new behavior is clearly wrong - documentation for ScreenSaverView says that it is a NSView subclass, and thus we should be able to override keyboard and mouse events.Submitted as FB6916019

What's the best way to submit 10.13 bugs? Anyone had better luck using bugreport.apple.com vs. Feedback Assistant?

Warning: It appears that Security Update 2020-005 is causing trouble with Screen Savers which are built using the Swift Runtime. Symptoms: after updating to Security Update 2020-005 on macOS 10.14 Mojave: Swift-built screensavers no longer funcion You will get a blank screen when the screensaver activates the first time. After the first time, the screensaver will revert to the default macOS screensaver Attempts to view the screensaver in System Preferences / Desktop & Screen Saver will give a blank page Crash logs indicate that the com.apple.preference.desktopscreeneffect.screeneffects.remoteservice process is crashing (see typical crash log below) Regression Testing: This happens on macOS 10.14.6 with Security Update 2020-005. We do not know if it affects other versions of macOS This affects personal or commercial screensavers built using iScreensaver ( iScreensaver.com ) but also seems to affect other screensavers such as the swift Clock.Saver found here: https://github.com/soffes/Clock.saver Typical Crash Log: Process:&#9;&#9;&#9;&#9;&#9;&#9;&#9; com.apple.preference.desktopscreeneffect.screeneffects.remoteservice [962] Path:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;/System/Library/PreferencePanes/DesktopScreenEffectsPref.prefPane/Contents/Resources/ScreenEffects.prefPane/Contents/XPCServices/com.apple.preference.desktopscreeneffect.screeneffects.remoteservice.xpc/Contents/MacOS/com.apple.preference.desktopscreeneffect.screeneffects.remoteservice Identifier:&#9;&#9;&#9;&#9;&#9;&#9;com.apple.preference.desktopscreeneffect.screeneffects.remoteservice Version:&#9;&#9;&#9;&#9;&#9;&#9;&#9; 1.0 (1) Build Info:&#9;&#9;&#9;&#9;&#9;&#9;DesktopScreenEffectsPref-229003000000000~20 Code Type:&#9;&#9;&#9;&#9;&#9;&#9; X86-64 (Native) Parent Process:&#9;&#9;&#9;&#9;??? [1] Responsible:&#9;&#9;&#9;&#9;&#9; System Preferences [955] User ID:&#9;&#9;&#9;&#9;&#9;&#9;&#9; 507 Date/Time:&#9;&#9;&#9;&#9;&#9;&#9; 2020-09-26 08:19:16.779 -0700 OS Version:&#9;&#9;&#9;&#9;&#9;&#9;Mac OS X 10.14.6 (18G6032) Report Version:&#9;&#9;&#9;&#9;12 Anonymous UUID:&#9;&#9;&#9;&#9;DA9B5F71-78EB-7DD2-F219-AF6A3A811FC1 Time Awake Since Boot: 1300 seconds System Integrity Protection: enabled Crashed Thread:&#9;&#9;&#9;&#9;0&#9;Dispatch queue: com.apple.main-thread Exception Type:&#9;&#9;&#9;&#9;EXC_BAD_ACCESS (SIGSEGV) Exception Codes:&#9;&#9;&#9; KERN_PROTECTION_FAILURE at 0x00007ffeef184ff8 Exception Note:&#9;&#9;&#9;&#9;EXC_CORPSE_NOTIFY Termination Signal:&#9;&#9;Segmentation fault: 11 Termination Reason:&#9;&#9;Namespace SIGNAL, Code 0xb Terminating Process:&#9; exc handler [962] VM Regions Near 0x7ffeef184ff8: &#9;&#9;MALLOC_SMALL&#9;&#9;&#9;&#9;&#9; 00007fc640000000-00007fc640800000 [ 8192K] rw-/rwx SM=PRV&#9;-> STACK GUARD&#9;&#9;&#9;&#9;&#9;&#9;00007ffeeb985000-00007ffeef185000 [ 56.0M] ---/rwx SM=NUL&#9;stack guard for thread 0 &#9;&#9;Stack&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;00007ffeef185000-00007ffeef985000 [ 8192K] rw-/rwx SM=SHM&#9;thread 0 Application Specific Signatures: Clock Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0&#9; libsystem_malloc.dylib&#9;&#9;&#9;&#9; 0x00007fff79a0fc95 malloc_zone_malloc + 99 1&#9; libsystem_malloc.dylib&#9;&#9;&#9;&#9; 0x00007fff79a0fc99 malloc_zone_malloc + 103 2&#9; libsystem_malloc.dylib&#9;&#9;&#9;&#9; 0x00007fff79a0fc99 malloc_zone_malloc + 103 3&#9; libsystem_malloc.dylib&#9;&#9;&#9;&#9; 0x00007fff79a0fc99 malloc_zone_malloc + 103 4&#9; libsystem_malloc.dylib&#9;&#9;&#9;&#9; 0x00007fff79a0fc99 malloc_zone_malloc + 103 [... this stack trace repeats for 511 entries ...]

This fails for me in Big Sur: open System/Library/PreferencePanes/DesktopScreenEffectsPref.prefPane The pane opens, but the list of screensavers is blank. Has anyone found a way to work around this? I've submitted this issue as FB8044776