When recovering from crash, frequent full sync's are necessary
Reported by Tim Cramer | August 30th, 2014 @ 06:25 PM
Comments and changes to this ticket
-
Tim Cramer August 30th, 2014 @ 06:30 PM
I've found that when MailMate does crash, there are options to either re-start mailmate to recover, or to re-sync the DB. Re-synching the DB for me with 330k messages takes hours (just for a simple consistency check). I have discovered, however, that the issue has always been that unsaved draft messages cause the re-sync to be required. If I choose not to import a message that was being composed, I can simply re-start mailmate and it comes back up without re-sync. This get's annoying for me as if I do searching for "Unquoted Body Text" (see related ticket also filed on 8/30/14) I get frequent crashes (about 25% of the time), and then any message that I'm composing is basically lost unless I don't want access to my email for hours as it syncs. This forces me back to gmail.com, which is awful :)
-
Tim Cramer August 30th, 2014 @ 06:33 PM
I'm running Version 1.8 (4214), on OS X 10.9.4, with 2.3 Ghz Intel Core i7 and 16GB of 1600 MHz DDR3 memory
-
benny September 3rd, 2014 @ 11:43 AM
- State changed from “new” to “fixcommitted”
Sorry about the loss of drafts. I believe the latest test release is faster at rebuilding (but it'll still be slow), but I also believe the crash bug has been fixed. Let me know if this is not the case.
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Mac OS X email client.
benny