<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class="">On Mar 20, 2017, at 11:39 AM, Jon Shier via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></blockquote><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>So when is this transition happening? The sooner the better, as Mail can’t really handle threads with large messages, like the recent evolution threads about Foundation serialization and decoding. It just stops rendering messages.</div></div></blockquote><br class=""></div><div>Huh, I figured I was the only one that happened to since the Radar I opened on that actually didn’t get marked as a duplicate (<a href="rdar://31137438" class="">rdar://31137438</a>). For me, it was worse than you describe; once I clicked on that thread, Mail would stop rendering messages from *any* thread, not just that one, and basically became non-functional until I quit the app and restarted it. The thread was quite the land mine, and I will admit to occasionally using some… colorful language after accidentally clicking on it.</div><div><br class=""></div><div>Charles</div><div><br class=""></div></body></html>