Crashes when importing email uncaught exception of type std::bad_alloc
Reported by Patrik Fältström | January 31st, 2014 @ 11:22 AM
Hi am just trying on recommendation from trusted friends MailMate. But it crashes already while importing email messages. I have from one of my friends heard it is questionable whether MailMate can handle "many" messages, and with "many" we talk about a few hundred thousand messages.
I have all my mail since 1997, archived in mailboxes, one per month. I do know that since 2001, when I started counting, I have 10-12k messages per month, i.e. between 100k and 140k messages per year -- for at least 14 years, which gives 1.5M messages or so.
Am I not a user MailMate likes? :-(
Patrik
Process: MailMate [43148]
Path: /Applications/MailMate.app/Contents/MacOS/MailMate
Identifier: com.freron.MailMate
Version: 1.7.2 (3905)
Code Type: X86 (Native)
Parent Process: launchd [289]
Responsible: MailMate [43148]
User ID: 501
Date/Time: 2014-01-31 12:09:30.984 +0100
OS Version: Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: 9DEAF783-EBE9-C119-3F5C-3487488DE22F
Crashed Thread: 15 IMAP connection
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
abort() called
Thread 0:: Dispatch queue: com.apple.main-thread
0 OakDatabase.dylib 0x00399995 std::insert_iterator<std::set<int, std::less<int>, std::allocator<int> > > std::set_union<std::_Rb_tree_const_iterator<int>, std::_Rb_tree_const_iterator<int>, std::insert_iterator<std::set<int, std::less<int>, std::allocator<int> > > >(std::_Rb_tree_const_iterator<int>, std::_Rb_tree_const_iterator<int>, std::_Rb_tree_const_iterator<int>, std::_Rb_tree_const_iterator<int>, std::insert_iterator<std::set<int, std::less<int>, std::allocator<int> > >) + 72
1 OakDatabase.dylib 0x003918d2 query::query_t::dispatch_changed_msg_ids(query::set_query_t*) + 162
2 OakDatabase.dylib 0x00391c68 query::query_t::add_remove_msg_ids(std::vector<int, std::allocator<int> > const&, std::vector<int, std::allocator<int> > const&) + 454
3 OakDatabase.dylib 0x00398a05 query::exists_query_t::update_msg_ids(std::vector<int, std::allocator<int> > const&, query::query_t*) + 309
4 OakDatabase.dylib 0x00394363 query::field_query_t::update_msg_ids(std::vector<int, std::allocator<int> > const&, query::query_t*) + 109
5 OakDatabase.dylib 0x00394418 query::field_query_t::did_change_headers(std::set<int, std::less<int>, std::allocator<int> > const&) + 158
6 OakDatabase.dylib 0x0039e4ff oracle_callback_t<query::field_query_callback_t>::did_change_headers(bool, std::set<int, std::less<int>, std::allocator<int> > const&) + 27
7 OakDatabase.dylib 0x00319663 header_oracle_t::perform_coalesced_callbacks(bool) + 61
8 OakDatabase.dylib 0x0031960a disable_oracle_coalescing() + 57
9 OakDatabase.dylib 0x0035336c imap_account_t::handle_data(std::tr1::shared_ptr<connection_result_t>) + 24192
10 OakProtocols.dylib 0x006b1ca5 connection_command_t::handle_reply(connection_command_t::result_t const&) + 239
11 OakProtocols.dylib 0x006b2ed6 oak::server_t<connection_command_t, std::tr1::shared_ptr<connection_t>, connection_command_t::result_t>::master_run() + 124
12 OakProtocols.dylib 0x006b1dcf cf::member_callback_t<oak::server_t<connection_command_t, std::tr1::shared_ptr<connection_t>, connection_command_t::result_t> >::member_callback_t(void (oak::server_t<connection_command_t, std::tr1::shared_ptr<connection_t>, connection_command_t::result_t>::*)(), oak::server_t<connection_command_t, std::tr1::shared_ptr<connection_t>, connection_command_t::result_t>*)::helper_t::wake_up(void*) + 33
13 com.apple.CoreFoundation 0x9b036e3f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
14 com.apple.CoreFoundation 0x9b027d95 __CFRunLoopDoSources0 + 437
15 com.apple.CoreFoundation 0x9b0273ce __CFRunLoopRun + 1022
16 com.apple.CoreFoundation 0x9b026d5a CFRunLoopRunSpecific + 394
17 com.apple.CoreFoundation 0x9b026bbb CFRunLoopRunInMode + 123
18 com.apple.HIToolbox 0x97cb1e2d RunCurrentEventLoopInMode + 259
19 com.apple.HIToolbox 0x97cb1bb2 ReceiveNextEventCommon + 526
20 com.apple.HIToolbox 0x97cb198d _BlockUntilNextEventMatchingListInModeWithFilter + 92
21 com.apple.AppKit 0x9954a5a9 _DPSNextEvent + 1602
22 com.apple.AppKit 0x99549ad0 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
23 com.apple.AppKit 0x9953c35c -[NSApplication run] + 727
24 com.apple.AppKit 0x995251f8 NSApplicationMain + 1165
25 com.freron.MailMate 0x0001eff7 main + 677
26 com.freron.MailMate 0x00002d95 start + 53
Comments and changes to this ticket
-
benny January 31st, 2014 @ 11:36 AM
- State changed from “new” to “bluesky”
Sorry, 1.5 million is out of reach for MailMate. My reply in this ticket describes my current view on what MailMate can handle.
If your primary activity is to search a large archive of emails then MailMate is not for you (I would suggest a simple online IMAP client although they might only really exist for use in the Terminal). If your primary activity is handling/replying a lot of incoming emails then you might consider having only the past 6-12 months of email in MailMate. MailMate allows you to subscribe to a subset of IMAP mailboxes (also without changing server side IMAP subscriptions).
You don't hold the record though. I was recently asked if MailMate could handle 10 million messages (40GB).
-
Patrik Fältström January 31st, 2014 @ 11:37 AM
Ok, thanks!!!
I normally use Mail.App -- but the number of bugs in the Mavericks version of the client have made me look around for something else... This was the reason why I "stumbled" on your client.
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