Closed RaitoBezarius closed 3 years ago
2020 prevented much development work on Mailspring, but rest assured, development has resumed!
Mailsync is something we particularly want to improve the stability of. Going through the GitHub Issues (would you believe it's at least 75% duplicates??), I've been able to isolate three major bugs so far:
https://community.getmailspring.com/t/the-eternal-sync-bug/334
https://community.getmailspring.com/t/disappearing-emails-desync/428
https://community.getmailspring.com/t/crash-on-sync-unknown-exception/419
https://community.getmailspring.com/t/syncfolderuidrange-errorconnection-on-one-of-the-folders/412
I've migrated your issue to Discourse as well:
https://community.getmailspring.com/t/mailsync-is-unstable-or-not-very-reliable-core-dumps/429
@RaitoBezarius Please join that community and comment on that article, and I'll reassign it to you so you get the credit.
We are in the process of migrating issues to Discourse, which can better facilitate discussion and discovery, and so GitHub Issues can focus on issues that are confirmed and slated for resolution in the near term. Learn more about the changes here.
We hope to see you there soon!
-The Mailspring Team
Describe the bug Across my usage of one year of MailSpring, I had 894 crashes of mailsync.bin and have 894 coredumps (
coredumpctl | grep -i /usr/share/mailspring/resources/app.asar.unpacked/mailsync.bin | wc -l
).Most of them have stack traces which looks like this:
Or more recently (4h ago):
To Reproduce Steps to reproduce the behavior:
coredumpctl
Expected behavior Known bugs or explanations on this. I don't think it's okay for a program to crash, neither it's really good for its "battery-friendly" aspect I believe.
Note:
As it is closed source, I am personally in the dark, I just cannot run gdb and try to understand or fix it properly. I understand the reasons behind a closed source tree, but really I think it should be possible to get access to the source code upon request while accepting that we will never bother you about support for it. Something between closed source & open source, or just close all bugs reports, I can read C++0x or whatever you use nowadays.
MailSync would be an awesome piece of code for the email landscape on Linux, I find this is a shame we cannot really see it. But that's not the purpose of this bug report.
Screenshots I could attach a tarball of my 894 coredumps (or whatever is still on my disk, after garbage collection/rotation).
Setup: (please complete the following information):
Additional context AFAIK, I don't know what could be the reason for this. I have 5 accounts to synchronize, also I have one inbox which is always synchronizing a folder and I don't understand why (everything is IMAP).