Mailspring lags with particularly large email threads or reply histories (> 25-30 replies). Turning off spell check mitigates this somewhat, although not completely.
On the GitHub thread, drholera reported that on Ubuntu 20.04, a thread with 35+ messages freezes the app completely.
Additional Context
This bug has been reported to exist even in Nylas Mail, and is confirmed as of 2020.
Is there any work related to this?
I have a thread with 88 emails on it, and growing, Mailspring doe snot permanently freezes, but it does take it some time to open it.
For me, generally viewing long thread is fine unless the quoted part of the email is not detected correctly by Mailspring so it displays everything instead of collapsing the quote.
What frustrated is when trying to reply to a long thread, Mailspring will froze that Iād have to force quit it.
Any update on this? Mailspring is by far the best email client on Linux, but this issue makes it un-usable for me. I have very long threads with some customers.
Iām bit by this exact issue over four different hardware configurations now, both Arch Linux and Mac OSX. I use a combination of gmail/self-hosted IMAP/google workspace. Whenever the threads start getting a bunch of replies, mailspring becomes unusable.
Can we do anything to assist in troubleshooting, enable more verbose debugging? Iāve been tracking the old github issue for years but nothing ever came of it. Would gladly spend time troubleshooting and reproducing if I knew how!
Tried many things to fix this to no avail, just wondering if the community can prioiritze this in anyways? This is a breaking point feature for me and iām sure many others as well.
Having the same issue since the beginning, itās really annoying, I have to wait for several minutes whenever I open a large threadā¦ Sometimes the app gets completely frozen and Iām forced to stop it.
The issue has been opened in 2019, when is it going to finaly be taken into account be Mailspringās team?
It was the best linux client until my thread have reached 35 replies. Now when I open the thread the program freezes and CPU works very hard and sometimes reaches 100%.
Think I have identified some ways of reducing the lag. Submitted a PR:
I saw that the unsubscribe link was causing MY hang on a thread. I saw that it was running some complex iterations to find unsubscribe links and decided to add a cache (as state changes made it do it all over again) and also ignore any links inside <blockquote> tags