Created attachment 442847 [details] Text contained in the Apple crash dialog OK. This is a weird one. We have an application, Vellum, that uses WKWebViews on Monterey to generate a PDF. I hit some very strange crashes in WebKit::DisplayLink::addObserver (see attached stack traces) as well as WebKit::DisplayLink::setPreferredFramesPerSecond (see attached screenshot – forgot to copy the text). Here’s the weird part: I could only get these crashes to occur when playing something via Spotify (!). In particular, I found that it happens when I am playing Shackleton’s “Something Tells Me / Pour Out Like Water” track off of “Departing Like Rivers” album (!!!). I tried other tracks on other albums, and couldn’t get it to happen. Now, I don’t think that this is Shackleton-specific (though wouldn’t that be a great bug?!). But maybe the fact that this track is 12 minutes long is affecting something? Why Spotify should be affecting OUR application, though, is a mystery. Since I hit these crashes in the Monterey Beta, we’ve noticed similar stack traces in our crash reporting database. So, this means that users who are now upgrading to Monterey are hitting this too. I haven’t tried to reproduce this yet via a smaller test app. If you are going to try to reproduce this issue, please let me know and I can provide you with an evaluation license so you can generate via Vellum. Here’s where you can download our application: https://vellum.pub It’s free to download, but you won’t be able to generate books without a license.
Created attachment 442848 [details] Text contained in the Apple crash dialog (second time)
Created attachment 442849 [details] Crash in slightly different location (forgot to grab text, but found this screenshot)
Simon/Tim: pretty sure this is a dupe of this? Plz shout at me if I'm wrong. *** This bug has been marked as a duplicate of bug 230917 ***
I really hope this is our bug, and am happy to see that (if it is) it has already been fixed. That said, this bug is affecting some of our uses pretty significantly right now. Is there anything we can do on our end that makes it less likely to hit this bug?
Sadly there isn't any workaround.
Bummer. I know it's unlikely...but is there any chance we might known when this fix will be incorporated into Monterey?
Also, in looking through our 120+ crashes, we've noticed that the crash only occurs in Monterey on NON-ARM chips. That is, we haven't seen any crashes on M1 machines. Figured I should update this bug, just in case that changes the likelihood that this bug is the same as the one its duped to.