Latest MailMate beta crash on launch.
Reported by macula | September 8th, 2018 @ 10:15 AM
Hi,
Running the latest beta version (downloaded today, 8 Sep 2018, from the website) on a late-2013 MBP, fully up-to-date software-wise (macOS 10.13.6).
Unfortunately, the app crashes while starting up (i.e. while the dock icon still bounces).
I downloaded and reinstalled it a second time, to no avail.
Is this an isolated incident or shall I wait for the next iteration? Is it possible to downgrade to the previous beta meanwhile?
Thanks.
Comments and changes to this ticket
-
benny September 10th, 2018 @ 06:16 AM
You can find the most recent test releases here: http://updates.mailmate-app.com/archives/
I'm not aware of a general issue and therefore I think it is some issue with your MailMate database. Please send me a crash report.
Also, if you know how to do it, you can try launching from a Terminal window to see if there are any error messages:
/Applications/MailMate.app/Contents/MacOS/MailMate
-
macula September 11th, 2018 @ 05:51 AM
Here is the error message produced when I launch the app from the command line, as you suggested;
Error: Offsets file (message-id) is corrupt at index 13099. Now what? ID: 126626, first: 2518081, last: 2518163 Segmentation fault: 11
It didn't start so badly but spiraled down after my attempt to rebuild the database, first from the cache, then from the server. Both attempts led to a crash and now I only get the aforementioned message, without even the prompt to rebuild.
I wouldn't want to lose my extensive MailMate settings (smart folders, key bindings, signatures, PGP keys, view settings, etc.) so I'm very reluctant to delete everything and reinstall from scratch, even with my preferences Application Support folder backed up.
Thanks —
-
benny September 11th, 2018 @ 06:52 AM
To get a clean start without losing settings then delete/remove everything but the
.plist
files (and maybe Resources if you have that) in this folder:/Users/<username>/Library/Application Support/MailMate/
Then launch MailMate and it should start refetching emails from the server(s).
Also save the
database.log
file for me if it exists. It might help me determine how this issue started. -
benny September 12th, 2018 @ 09:00 AM
- State changed from new to cantreproduce
The issue was resolved by email, but it was not possible to reproduce it.
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 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.