topher1078 wrote:Weird problem just wanted to make everyone aware of. Just installed the hot-off-the-presses Safari 4 beta. Mail opened, but then froze a few seconds after, and the error dialog box blamed GrowlMail.
Yup. Workarounds in my blog post:
http://boredzo.org/blog/archives/2009-02-24/safari-4-beta-and-growlmail. (You guys seem to have already found one of them, but I show another that doesn't require a trip through the Terminal. See also this blog post <
http://hajimemasita.blogspot.com/2009/02/safari4-public-betamailapp.html>, which has a screenshot—the text is in Japanese, but you can figure out the screenshot.)
So either Safari 4 Beta is messing with Growl system wide (doesn't seem too though as other notifications are still working) or changes something in Mail (which seems strange, maybe it's updating the web rendering engine within Mail or something).
Neither one. Mail uses WebKit to display messages, and one of the changes in Safari 4's new WebKit is stricter enforcement of which thread you call it on. We call a method named attributedString in Mail; it calls WebKit's method; WebKit's method raises an exception because we (indirectly) called it from a secondary thread.
I have already created a fix and proven that it works. I've sent the patches to the other developers for review; if I hear nothing bad about them by tomorrow, I'll put them into the repository as part of 1.1.5.
Before anyone asks: No timeline on 1.1.5. I'd like to get it out there sooner rather than later, though.