crash while dragging more than 1000 messages
Reported by Eli Rotenberg | September 14th, 2021 @ 05:47 AM
new user here, testing out your software, and reporting that I cannot option-drag more than some few hundreds of emails from one server's inbox to an archival imap server that I am running in my home. I could option-drag some several hundred at a time repeatedly but random crashes occur somewhere around 900 or more messages.
the observed behavior is:
- wait until any ongoing transfer is finished (don't know if needed
or can add actions like this to a queue) - option-drag around 1000
messages until destination folder is highlighted. - let go of mouse
- if colored beachball mouse icon appears, then it crashes a few
seconds later. if colored beachball does not appear, the messages
have always copied it seems.
I have not tested regular (non-option-key) dragging, I am afraid
it will lose my messages if it crashes.
It is generally not a problem to copy thousands of messages at a
time doing the same move with thunderbird, so I don't think my
destination imap server is at fault.
thank you very much for an impressive program. I hope that I can purchase it soon but achieving large-batch, reliable message copies are the main reason I am looking for a new app.
Eli
Comments and changes to this ticket
-
Eli Rotenberg September 14th, 2021 @ 05:53 AM
Additional notes:
- There is no particular problematic message. If after crashing I
break it up into smaller batches, I can get all the emails to
copy.
- Usually when it crashes something like 3 to 6 messages did
transfer.
- Crashes similarly if dragging from an INBOX or a smart
mailbox.
- I don't know if there is a specific fail point. Since I paid
attention, under 600 messages has never crashed so I don't think
crashes are purely random. Over 1000 has always crashed. I got
930-something to work once.
- I could get several concurrent moves, each > 500 messages, and none of them crashed, so it seems not a memory issue.
Here is an example "problem report" while dragging about 1018 messages as an example.
I am only sending the opening lines, if you want the full report I will reproduce the problem and send another report in full. But perhaps Apple has sent this report to you already.
Process: MailMate [50178]
Path: /Applications/MailMate.app/Contents/MacOS/MailMate
Identifier: com.freron.MailMate
Version: 1.13.2 (5673)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: MailMate [50178]
User ID: 501Date/Time: 2021-09-13 22:48:49.182 -0700
OS Version: Mac OS X 10.15.6 (19G2021)
Report Version: 12
Bridge OS Version: 4.6 (17P6610)
Anonymous UUID: 24C17CDB-3CA3-B0D9-98E9-70F6D89E2280Sleep/Wake UUID: D0B79014-EEC0-4966-93B0-951BC4CE2119
Time Awake Since Boot: 970000 seconds
Time Since Wake: 5800 secondsSystem Integrity Protection: enabled
Crashed Thread: 1 JavaScriptCore bmalloc scavenger
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFYTermination Reason: Namespace OBJC, Code 0x1
Application Specific Information:
autorelease pool page 0x7fb6cb809000 corrupted
magic 0x00000000 0x00000000 0x00000000 0x00000000 should be 0xa1a1a1a1 0x4f545541 0x454c4552 0x21455341 pthread 0x11497edc0 should be 0x11497edc0 Assertion failed: (NSViewIsCurrentlyBuildingLayerTreeForDisplay() != currentlyBuildingLayerTree), function NSViewSetCurrentlyBuildingLayerTreeForDisplay, file /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1894.60.100/AppKit.subproj/NSView.m, line 13568. - There is no particular problematic message. If after crashing I
break it up into smaller batches, I can get all the emails to
copy.
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