Slow delete

Oracle RAC 10.2.0.4 on RHEL 5.
I do not understand this situation: I have a table A with 60 million rows and an index A_IDX on column C1 of table A.
If I run
select sum (C2) from A where C1 = 'XXX';
being C2 another column of A, the query returns in 20 seconds, performing an index range scan of A_IDX.
If I run
delete from A where C1 = 'XXX';
the query performs the same index range scan on A_IDX but runs for days waiting on db file scattered read.
The records to be deleted are only 300,000 so undo/redo generated should not influence the DELETE performance.
Any suggestion on the reason for this waits?
Regards

Ask your self if you have
(a) delete trigger on table A
(b) foreign key intergirty constraints in table A
As this might influence the delete time
Best Regards
Mohamed Houri

Similar Messages

Slow delete whether or not deleted singly or as a group

During performance analysis for my project I found some code where deletes from table y (I will call it), were being deleted in a loop, thus deleting one record at a time where there are approx. 87,000 records to delete. Table y has 200 million records. I rewrote the code to do a delete by internal table, i.e. DELETE y FROM TABLE t_y, to delete all 87,000 records at once. The strange thing that is happening is that the deletes take about the same time whether it is a one by one delete or all at once by internal table, ~40ms per deleted record. The delete by internal table shows in the job statistics and ST05 that it is processing 256 records at a time, so there are 340 items in the trace for the DELETE (340 * 256 ~= 87,000). All of the reads, updates, and selects take about 1ms per record. The internal table (t_y) is typed exactly like the transparent table. All of the records requested to be deleted are in the table y and there are no duplicates in the internal table.
Old Code:
LOOP AT t_y.
DELETE y FROM t_y.
ENDLOOP.
New Code:
DELETE y FROM TABLE t_y.
It takes approx. 1 hour to delete 87,000 records. So the question is why deleting all records has the same speed as deleting one by one. Secondarily, why is the system only sending 256 ercords at a time to be deleted.
Thanks,
Andy Goerdel

Hi Andy,
> one by one delete or all at once by internal table, ~40ms per deleted record.
> updates, and selects take about 1ms per record
first of all the delete has to touch the table and all indexes which is not the case for select and not necessarily for the update.
So depending on the number of indexes defined a delete has to be slower than a select or an update (which does not touch all rows) because it has to do more i/o.
> It takes approx. 1 hour to delete 87,000 records. So the question is why deleting all records has the same speed as
> deleting one by one.
that is an interesting one. One should assume that the array processing should be sligthly faster... .
> Secondarily, why is the system only sending 256 records at a time to be deleted.
The SAP application server communicates in blocks (size depends... could be 32, 40, 64 or 128) with the database.
The key fields for the delete are filled in such a block until it is full. You have no influence here.
How much indexes are defined on your table? The 40 ms is most likely driven by physical i/o for table and index blocks.
The amount of i/o that needs to be done is the same for one by one or for array processing. The array interface only
redcues the number of calls. Obviously these savings are relatively small compared to the i/o that needs to be done
in any case.
With ST04 you can check how much physiscal i/os are redquired for your deletes.
Kind regards,
Hermann

My macbook seems to be running slow deleted bunch of stuff and pictures and close things not in use i have 889mb wired 1.94gb active 323mb inactive and 879mb free idk what that all means but hopefully someone can tell me

deleted bunch of stuff and pictures and close things not in use i have 889mb wired 1.94gb active 323mb inactive and 879mb free idk what that all means but hopefully someone can tell me. is there a program i can use and fix it or if its easy can i do it myself

macworld.com/mac-troubleshooting-what-to-do-when-your -computer-is-too-slow.
Basically... Make sure you have enough Free Hard Drive space for your Mac to Perform as expected...

Trash is slow deleting files

Hi, My trash is deleting files but its really slow. Maybe around 1 file a minute. Something is obviously wrong. Any ideas?
Cheers
It's a 17inch mac book pro

It sounds like you have secure empty trash selected.
Solution:
open Finder Preferences>advanced>and make sure "empty trash securely" is unchecked.

Mavericks Mail slow - deletes and updates

I have two exchange accounts and a gmail account in mail. Until the Mavericks update, I had to force quit mail at least once per day. That hasn't happened yet. HOWEVER, If the focus is in the message in the preview pane and not on the message header in the message list, delete doesn't work at all. If I click on the header, it will eventually delete, but takes a few seconds.
Any others with this issue?

Hello there, SeamusMcG.
The following Knowledge Base article offers some pointers for determining what may be causing the slowness:
OS X Mavericks: If your Mac runs slowly
http://support.apple.com/kb/PH13895
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Painfully Slow Deletion

I am aware this has been mentioned in other threads and the on going issue with having "auto write metadata", but I wanted to check if anyone knows why deleting from within LR is 100 times slower than deleting in windows and resyncing. In theory that is all the delete should be, but it seems LR is taking a very long winded approach. I am using a Vista PC with 4GB RAM, about 10,000 images and "auto write" turned off.
I am now using a new policy to delete anything more than a few images.
1. Rename images Delete-1 etc
2. Go to explorer and delete images & sidecars
3. Resync LR
This seems to work and miles faster, but does anyone know if this is a bad idea for some reason?
If anyone from Adobe is reading this you have to agree this is unbeleivably dysfunctional activity for such a common task!!!

Approximately how many photos are you deleting when you experience long elapsed times? (1oo times -- two orders of magnitude -- slower is somewhat hard to believe.)
My workflow is to mark images destined to the dust bin with a reject flag. I hide these rejects by setting a filter to view only Picks and Unflagged Photos. When I'm ready to delete I choose the Images>Delete Rejected Photos menu item. If, in your case, deletes take a long time just choose this delete option during "idle" times (e.g. when away from the computer grabbing a midnight caffeine fix.)

Extremely slow deleting / modifying of files

Hi all,
I have a strange problem with windows 7 in combination with server 2008 R2.
Situation.
1] I copy a bunch of files to the server (UNC of mapped driver) with W7 (32 or 64 bits professional.)
2] I want to delete the files i've just copied (same issue with modification) it is extremely slow. Only 1 file per second
sometimes even slower.
When I perform the same actions with Vista or XP it is extremely fast. For vista I had to switch off Remote Differential Compression.
I did this also for W7 but no improvement. Delete files with the W7 machine is also fast when copied to the server from the vista or xp
machine. I've tried serveral new machines with W7 but all show the same problems.
Any help is welcome,
with kind regards
Roland

Try Fred Langa's fix @ http://windowssecrets.com/2010/10/14/01:
"<big>Easy steps to a significantly faster network
</big> <small>
</small> To start, if you're in a homegroup, exit it. (Need info? See MS's Help
page , "Leave a homegroup.") Once every PC has left the homegroup, it no longer exists.
Next, to disable HomeGroup and change encryption levels, open the Control Panel, select
Network and Internet, then Network and Sharing Center. Once there, in the left-hand pane choose
Change advanced sharing settings.
It's a two-click fix, as shown in Figure 1.
Figure 1. Two quick radio-button clicks are all it takes to restore classic networking speed to Windows 7.
In the Home or Work section of the dialog box, scroll down to File Sharing Connections and click the radio button for
Enable file sharing for devices that use 40- or 56-bit encryption. (Note: You need this setting anyway, if you want to share files between Win7 and an XP box. More on this to come.)
Next, a bit further down under HomeGroup connections, select
Use user accounts and passwords to connect to other computers.
Save the changes, and you're done!"

Slow delete on a table with one CLOB column

Hi,
I have a table which has one CLOB column and even if I delete one row from it, it takes approx. 16 seconds. Since UNDO isn't generated for CLOBs (at least not in the UNDO tablespace), I can't figure out why this is so? The CLOB has defined a RETENTION clause, so it depends upon UNDO_RETENTION which is set to 900. There wasn't any lock from another session present on this table.
The table currently contains only 6 rows but it used to be bigger in the past, so I thought that maybe a full table scan is going on when deleting. But even if I limit the DELETE statement with an ROWID (to avoid a FTS), it doesn't help:
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
PL/SQL Release 11.1.0.6.0 - Production
CORE    11.1.0.6.0      Production
TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - Production
SQL> select count(*) from scott.packet;
COUNT(*)
         6
SQL> column segment_name format a30
SQL> select segment_name
2    from dba_lobs
3 where owner = 'SCOTT'
4     and table_name = 'PACKET';
SEGMENT_NAME
SYS_LOB0000081487C00002$$
SQL> select segment_name, bytes/1024/1024 MB
2    from dba_segments
3 where owner = 'SCOTT'
4      and segment_name in ('PACKET', 'SYS_LOB0000081487C00002$$');
SEGMENT_NAME                           MB
PACKET                               ,4375
SYS_LOB0000081487C00002$$             576
SQL> -- packet_xml is the CLOB column
SQL> select sum(dbms_lob.getlength (packet_xml))/1024/1024 MB from scott.packet;
        MB
19,8279037
SQL> column rowid new_value rid
SQL> select rowid from scott.packet where rownum=1;
ROWID
AAAT5PAAEAAEEDHAAN
SQL> set timing on
SQL> delete from scott.packet where rowid = '&rid';
old   1: delete from scott.packet where rowid = '&rid'
new   1: delete from scott.packet where rowid = 'AAAT5PAAEAAEEDHAAN'
1 row deleted.
Elapsed: 00:00:15.64From another session I monitored v$session.event for the session performing the DELETE and the reported wait event was 'db file scattered read'.
Someone asked Jonathan Lewis a similar looking question (under comment #5) here: http://jonathanlewis.wordpress.com/2007/05/11/lob-sizing/ but unfortunately I couldn't find if he wrote any answer/note about that.
So if anyone has any suggestion, I'll appreciate it very much.
Regards,
Jure

After reviewing the tkprof as suggested by user503699, I noticed that the DELETE itself is instantaneous. The problem is another statement:
select /*+ all_rows */ count(1)
from
"SCOTT"."MESSAGES" where "PACKET_ID" = :1
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          2           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1      1.40      16.93     125012     125128          0           1
total        3      1.40      16.93     125012     125128          2           1
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: ALL_ROWS
Parsing user id: SYS   (recursive depth: 1)
Rows     Row Source Operation
      1 SORT AGGREGATE (cr=125128 pr=125012 pw=125012 time=0 us)
      0   TABLE ACCESS FULL MESSAGES (cr=125128 pr=125012 pw=125012 time=0 us cost=32900 size=23056 card=5764)I checked if there was any "ON DELETE" trigger and since there wasn't, I suspected this might be a problem of unindexed foreign keys. As soon as I created an index on SCOTT.MESSAGES.PACKET_ID the DELETE executed immediately. The "funny" thing is that, the table SCOTT.MESSAGES is empty, but it has allocated 984MB of extents (since it wasn't truncated), so a time consuming full tablescan was occurring on it.
Thanks for pointing me to the 10046 trace which solved the problem.
Regards,
Jure

Possibly solution to slow deleting if using Kapersky Internet Security

In case anyone has a similr problem i discovered today that the File AV within Kersky Internet Security 2010 is killing the process when deelting files making it take forever. The solutions I have found so far are:
a) Turn off the File AV completely under settings
b)There is an option under File AV / settings/additional go to "pause on application startup" click select and at the exe.
Hope that helps someone
Mike

FWIW, I have a similar problem with Webroot's Spy Sweeper - it seems to kill MOVE and DELETE performance.
When I've had to copy 100's or 1000's of large files, it will crawl and Windows will report "4 hours remaining"... I turn off the A/V and all of a sudden it's "2 minutes remaining".

Super slow deleting and opening emails

I've done everything from uninstalling/reinstalling, disabling all add ons, deleting msf files, running safe mode. thunderbird is almost dead at this point. anytime I try opening or closing, deleting I get the "not responding" message. please don't make me have to start using another email package. How can I completely remove all of my thunderbird info off my hard drive and start over?
cheers
Bart

I turned off the email scan function in mcafee and all is well thanks. it's right click on mcafee icon (lower right of screen)>change settings>settings>unclick email attachments>apply
cheers
Bart

Slow delete, slow upload, slow, slow, slow...

Hello,
I've bought a Macbook Air. Please can someone tell me why it takes so long to delete, amend or move files? In iTunes, I have nearly every song duplicated (really no idea why iTunes has done that), so I need to get rid of them. Even just amending the genre of an album makes the bar appear on screen for me to watch and wait. It's quite frustrating for the amount of money this machine costs.
Cheers, Mike

Oh, ok. That is what I did. There is more info now; I hope this isn't too much to send.
16/08/2014 22:36:16.430 apsd[85]: Unrecognized leaf certificate
16/08/2014 22:44:23.540 xpcproxy[33704]: assertion failed: 13E28: xpcproxy + 3438 [D559FC96-E6B1-363A-B850-C7AC9734F210]: 0x2
16/08/2014 22:51:37.286 apsd[85]: Unrecognized leaf certificate
16/08/2014 22:56:45.246 usbmuxd[50]: lockssl_handshake (thread 0x100787000): SSL handshake controlled failure 0: SSL_ERROR_SYSCALL (Early EOF reached)
16/08/2014 22:56:45.248 usbmuxd[50]: AMDeviceStartSession (thread 0x100787000): Could not start session: kAMDDeviceDisconnectedError
16/08/2014 22:56:45.248 com.apple.usbmuxd[50]: HandleUSBMuxConnect Client 0x100312d00-usbmuxd/NULL requesting attach to 0x2:62078 failed, no such device
16/08/2014 22:56:45.249 usbmuxd[50]: AMDeviceConnect (thread 0x100787000): Could not connect to lockdown port (62078) on device 2 - 1ba097ee7f79e1fef699c1cd340c26b8856c3864: 0xe8000084.
16/08/2014 22:56:45.249 usbmuxd[50]: device_os_is_at_least (thread 0x100787000): AMDeviceConnect failed: 0xe8000084
16/08/2014 22:56:45.249 usbmuxd[50]: _AMDevicePreflightWorker (thread 0x100787000): Pair worker could not pair with device 2: 0xe8000084
16/08/2014 22:56:47.001 PTPCamera[33732]: waitForCallbackThreadConditionSignalWithTimeout: pthread_cond_timedwait() failed, status = 60
16/08/2014 22:58:32.987 iTunesHelper[263]: _receive_message (thread 0x7fff76b78310): Far end closed connection: Operation not supported on socket
16/08/2014 22:58:55.952 iTunesHelper[263]: AMDeviceConnect (thread 0x7fff76b78310): Could not connect to lockdown port (62078) on device 11 - 1ba097ee7f79e1fef699c1cd340c26b8856c3864: 0xe8000084.
16/08/2014 22:59:19.510 usbmuxd[50]: lockssl_handshake (thread 0x100787000): SSL handshake controlled failure 0: SSL_ERROR_SYSCALL (Early EOF reached)
16/08/2014 22:59:19.511 usbmuxd[50]: AMDeviceStartSession (thread 0x100787000): Could not start session: kAMDDeviceDisconnectedError
16/08/2014 22:59:19.511 com.apple.usbmuxd[50]: HandleUSBMuxConnect Client 0x100501e60-usbmuxd/NULL requesting attach to 0xe:62078 failed, no such device
16/08/2014 22:59:19.512 usbmuxd[50]: AMDeviceConnect (thread 0x100787000): Could not connect to lockdown port (62078) on device 14 - 1ba097ee7f79e1fef699c1cd340c26b8856c3864: 0xe8000084.
16/08/2014 22:59:19.512 usbmuxd[50]: device_os_is_at_least (thread 0x100787000): AMDeviceConnect failed: 0xe8000084
16/08/2014 22:59:19.512 usbmuxd[50]: _AMDevicePreflightWorker (thread 0x100787000): Pair worker could not pair with device 14: 0xe8000084
16/08/2014 22:59:20.696 usbmuxd[50]: _receive_message (thread 0x100787000): Far end closed connection: Undefined error: 0
16/08/2014 22:59:20.697 usbmuxd[50]: _AMDevicePreflightWorker (thread 0x100787000): Pair worker could not connect to lockdownd on device 16: 0xe8000084.
16/08/2014 22:59:21.103 usbmuxd[50]: _receive_message (thread 0x100787000): Far end closed connection: Undefined error: 0
16/08/2014 22:59:21.104 usbmuxd[50]: _AMDevicePreflightWorker (thread 0x100787000): Pair worker could not connect to lockdownd on device 17: 0xe8000084.
16/08/2014 23:01:37.917 usbmuxd[50]: lockssl_handshake (thread 0x100787000): SSL handshake controlled failure 0: SSL_ERROR_SYSCALL (Early EOF reached)
16/08/2014 23:01:37.918 usbmuxd[50]: AMDeviceStartSession (thread 0x100787000): Could not start session: kAMDDeviceDisconnectedError
16/08/2014 23:01:37.918 com.apple.usbmuxd[50]: HandleUSBMuxConnect Client 0x100210ef0-usbmuxd/NULL requesting attach to 0x16:62078 failed, no such device
16/08/2014 23:01:37.919 usbmuxd[50]: AMDeviceConnect (thread 0x100787000): Could not connect to lockdown port (62078) on device 22 - 1ba097ee7f79e1fef699c1cd340c26b8856c3864: 0xe8000084.
16/08/2014 23:01:37.919 usbmuxd[50]: device_os_is_at_least (thread 0x100787000): AMDeviceConnect failed: 0xe8000084
16/08/2014 23:01:37.919 usbmuxd[50]: _AMDevicePreflightWorker (thread 0x100787000): Pair worker could not pair with device 22: 0xe8000084
16/08/2014 23:01:38.306 usbmuxd[50]: lockssl_handshake (thread 0x100787000): SSL handshake fatal lower level error -1: SSL_ERROR_SYSCALL errno (Broken pipe)
16/08/2014 23:01:38.306 usbmuxd[50]: AMDeviceStartSession (thread 0x100787000): Could not start session: kAMDDeviceDisconnectedError
16/08/2014 23:01:38.307 com.apple.usbmuxd[50]: HandleUSBMuxConnect Client 0x1002102c0-usbmuxd/NULL requesting attach to 0x17:62078 failed, no such device
16/08/2014 23:01:38.307 usbmuxd[50]: AMDeviceConnect (thread 0x100787000): Could not connect to lockdown port (62078) on device 23 - 1ba097ee7f79e1fef699c1cd340c26b8856c3864: 0xe8000084.
16/08/2014 23:01:38.308 usbmuxd[50]: device_os_is_at_least (thread 0x100787000): AMDeviceConnect failed: 0xe8000084
16/08/2014 23:01:38.308 usbmuxd[50]: _AMDevicePreflightWorker (thread 0x100787000): Pair worker could not pair with device 23: 0xe8000084
16/08/2014 23:02:54.520 usbmuxd[50]: _receive_message (thread 0x100787000): Far end closed connection: Undefined error: 0
16/08/2014 23:02:54.521 usbmuxd[50]: AMDeviceStartSession (thread 0x100787000): Could not start session: kAMDDeviceDisconnectedError
16/08/2014 23:02:54.521 com.apple.usbmuxd[50]: HandleUSBMuxConnect Client 0x1002102c0-usbmuxd/NULL requesting attach to 0x24:62078 failed, no such device
16/08/2014 23:02:54.522 usbmuxd[50]: AMDeviceConnect (thread 0x100787000): Could not connect to lockdown port (62078) on device 36 - 1ba097ee7f79e1fef699c1cd340c26b8856c3864: 0xe8000084.
16/08/2014 23:02:54.522 usbmuxd[50]: device_os_is_at_least (thread 0x100787000): AMDeviceConnect failed: 0xe8000084
16/08/2014 23:02:54.522 usbmuxd[50]: _AMDevicePreflightWorker (thread 0x100787000): Pair worker could not pair with device 36: 0xe8000084
16/08/2014 23:06:58.093 apsd[85]: Unrecognized leaf certificate
16/08/2014 23:16:44.874 xpcproxy[33780]: assertion failed: 13E28: xpcproxy + 3438 [D559FC96-E6B1-363A-B850-C7AC9734F210]: 0x2
16/08/2014 23:22:18.897 apsd[85]: Unrecognized leaf certificate

Xserve RAID, xfs, linux, and VERY slow deletes

Greetings,
We're running a linux box with kernel 2.6.22-2-amd64 on dual AMD Opteron Processors with 8G ram. We have two xserve raids mounted on this box: one with 4.1T (called gala) and another with 1.9T (called apple). We serve these disks to other boxen via nfs.
I have a series of large files (about 5G each) that I want to delete from the disk apple. I ssh to the machine to which the disks are attached (ie not via nfs). I change into the directory where the disk is mounted and sudo rm -rf *.gz. The first cpu on the box goes to 100% and it takes something like 15 minutes to delete EACH 5G file.
I've googled around but found no solution as to why this is hapening or what I can do about it.
The disk is mounted with no options:
/dev/sdd1 on /storage/disks/apple type xfs (rw)
Can someone help?
Thanks!

The depth of this directory is 1. That is:
dir$ ls -1
bigfile1.gz
bigfine2.gz
dir$
There are no subdirectories.
dir$ rm bigfile1.gz
takes about 10 minutes where bigfile1.gz is about 5GB in size.
I have not done the math to decide if the time is proportional to size because I wasn't sure how xfs deals with sparse files.
Thanks for any help anybody can provide.
Chad Matsalla

Very slow internet after installing 10.5.3

Hello all, this is the very first time I have encountered any problems with my Macbook and I am hoping I can get some help here.
About a month ago I came home from college and hooked my Macbook up to the wireless router at home, everything was running fine. We have fiber optic internet so usually my speeds are blazing fast. Recently however I installed the 10.5.3 update and now my internet speeds are very dismal. I am having trouble getting my Macbook to connect to the router at all, much less load any web pages.
I have taken an ethernet cable and plugged my Macbook directly in to the router to see if things load any faster, and unfortunately things are still just as slow over a wired connection. After typing in a URL you will sit there at a blank web page for about 45 seconds to a minute before it even starts loading the page, and when the page does load it takes forever to pull up and images take even longer to display. If it helps at all our router is a dlink DI-524 wireless router.
I was browsing through these forums yesterday to see if I could find a solution to my issue. so far I have tried the following:
-set router to broadcast in G mode only (instead of mixed mode)
-removed encryption from router
-tried various encryption settings (64 bit WEP, 128 bit WEP, WPA, etc)
-updated the firmware of my router
-created test account on my macbook, opened internet browser on it, everything still runs slow
-deleted cache for safari/mozilla as well as the .plist files, still slow internet
when i called apple the agent suggested putting in my os X CD and do an archive and install, i did and once i was set back to os X 10.5 i was unable to connect to wifi at all, and wired connection over ethernet seemed just as slow as before. when i check for apple updates the 10.5.3 update was my only option, i couldnt choose 10.5.2 so installing that would put me back where i was before.
in the end i set my computer up last night to do a restore from my time machine backup. my machine has been restored to the backup i created just before i tried the archive and install, so im back to running OS X 10.5.3 now.
I'm sorry this post got so long, I just wanted to make sure that I included details of what I've done so far. Again I would like to stress that I am having this problem on my macbook even with my computer hooked directly to the router with my ethernet cable. (using that same cable and hooking up any one of my windows computers in the house results in fast and effortless web browsing so i know the cable is good)

It's not a matter of Mac OS X being "picky" but rather various ISPs not keeping up with changes in the DNS standard.
In the most recent case, 10.5.3 had to revert to a previous method of performing some DNS lookups because various ISPs hadn't bothered to update their servers to handle what has been the recommended way of handling lookups for the past eight years.
OpenDNS also has done a lot of work to make sure their DNS servers work as fast as possible; ISPs have absolutely no incentive whatsoever to provide fast DNS services.

How do I improve performance while doing pull, push and delete from Azure Storage Queue

Hi,
I am working on a distributed application with Azure Storage Queue for message queuing. queue will be used by multiple clients across the clock and thus it is expected that it would be heavily loaded most on the time in usage. business case is typical as in
it pulls message from queue, process the message then deletes the message from queue. this module also sends back a notification to user indicating process is complete. functions/modules work fine as in they meet the logical requirement. pretty typical queue
scenario.
Now, coming to the problem statement. since it is envisaged that the queue would be heavily loaded most of the time, I am pushing towards to speed up processing of the overall message lifetime. the faster I can clear messages, the better overall experience
it would be for everyone, system and users.
To improve on performance I did multiple cycles for performance profiling and then improving on the identified "HOT" path/function.
It all came down to a point where only the Azure Queue pull and delete are the only two most time consuming calls outside. I can further improve on pull, which i did by batch pulling 32 message at a time (which is the max message count i can pull from Azure
queue at once at the time of writing this question.), this returned me a favor as in by reducing processing time to a big margin. all good till this as well.
i am processing these messages in parallel so as to improve on overall performance.
pseudo code:
//AzureQueue Class is encapsulating calls to Azure Storage Queue.
//assume nothing fancy inside, vanila calls to queue for pull/push/delete
var batchMessages = AzureQueue.Pull(32); Parallel.ForEach(batchMessages, bMessage =>
//DoSomething does some background processing;
try{DoSomething(bMessage);}
catch()
//Log exception
AzureQueue.Delete(bMessage);
With this change now, profiling results show that up-to 90% of time is only taken by the Azure Message delete calls. As it is good to delete message as soon as processing is done, i remove it just after "DoSomething" is finished.
what i need now is suggestions on how to further improve performance of this function when 90% of the time is being eaten up by the Azure Queue Delete call itself? is there a better faster way to perform delete/bulk delete etc?
with the implementation mentioned here, i get speed of close to 25 messages/sec. Right now Azure queue delete calls are choking application performance. so is there any hope to push it further.
Does it also makes difference in performance which queue delete call am making? as of now queue has overloaded method for deleting message, one which except message object and another which accepts message identifier and pop receipt. i am using the later
one here with message identifier nad pop receipt to delete message from queue.
Let me know if you need any additional information or any clarification in question.
Inputs/suggestions are welcome.
Many thanks.

The first thing that came to mind was to use a parallel delete at the same time you run the work in DoSomething. If DoSomething fails, add the message back into the queue. This won't work for every application, and work that was in the queue
near the head could be pushed back to the tail, so you'd have to think about how that may effect your workload.
Or, make a threadpool queued delete after the work was successful. Fire and forget. However, if you're loading the processing at 25/sec, and 90% of time sits on the delete, you'd quickly accumulate delete calls for the threadpool until you'd
never catch up. At 70-80% duty cycle this may work, but the closer you get to always being busy could make this dangerous.
I wonder if calling the delete REST API yourself may offer any improvements. If you find the delete sets up a TCP connection each time, this may be all you need. Try to keep the connection open, or see if the REST API can delete more at a time
than the SDK API can.
Or, if you have the funds, just have more VM instances doing the work in parallel, so the first machine handles 25/sec, the second at 25/sec also - and you just live with the slow delete. If that's still not good enough, add more instances.
Darin R.

Mail on Yosemite: crashes, slow and buggy.

I have already posted my experiences with Mail on Yosemite on several threads, and now I have decided to open my own thread about it, with the hope that Apple sees how many users are having the same kind of issues, and hopefully will address them in the next OS update.
Keep in mind that I am a web computer programmer, therefore I know, and I am sure that there is something buggy with this new version of Mail compared with the one on Mavericks, and I am sure Apple can fix it.
Here are the major flaws I have experienced:
1. Mail sometimes crashes, even when just typing a message which gives me frustration and madness!
2. Mail fetching and sending is terribly slow. New mail appears inside Mail after several minutes it is already appeared on my iPhone.
3. Updating the mailbox counters take forever. I have to literally leave Mail open for 15-20 minutes to see slowly updating the mailbox counters (!!!) That creates a lot of confusion from my part.
4. Slow deletion: If I delete 10 messages in a row inside a mailbox, then I go working on a different mailbox, and then get back to the previous one, the just deleted messages are back there! And they are getting "slowly" deleted after several minutes (10-20 minutes?)...
Well, it's impossible to work this way, it is just a mess. Managing email with my iPhone is much easier, which is insane.
The Activity window is always "working" with several processes going on all the time, no idea if that's normal or what. Why in the heck Mail has to keep synching a mailbox with inside just 20 emails for over 20 minutes??!!
I really hope Apple is going to release an update to fix all these issues, otherwise I will have to downgrade back to Mavericks. For me, actually, moving from Mavericks to Yosemite has been a big downgrade of performance, and a waste of time (hours!!) to figure out issues like this one.
My computer is a 2009 Mac Pro Quad-Core Xeon with 32GB ram, which has an insane amount of ram to have crashes and slowness with a simple program like Mail (!!) I have already tried everything: cleaning caches, regular OS maintenance, cleaning, rebooting in safe mode, reconfiguring Mail from scratch, etc. Something is wrong with the program itself.
If anyone is experiencing this kind of issues, please, post your experience on this thread, so we can have more chances to be noticed by Apple (if they ever look at these forums...)
Thanks in advance, and let's keep Mac OS improving!!
Best,
Fab.

Thank you Linc for your idea of posting logs, here they are:
CONSOLE MESSAGES:
I found a lot of "No worthy mechs found" lines for Mail, and I am pasting here below messages logged during m,y last crashes yesterday morning, they appear related to fonts (I have already checked duplicates with font-book!):
12/15/14 10:11:29.281 AM Mail[3223]: No worthy mechs found
12/15/14 10:11:29.786 AM Mail[3223]: No worthy mechs found
12/15/14 10:11:33.940 AM Mail[3223]: No worthy mechs found
12/15/14 10:11:38.500 AM Mail[3223]: No worthy mechs found
12/15/14 10:11:38.955 AM Mail[3223]: No worthy mechs found
12/15/14 10:11:39.796 AM Mail[3223]: Could not load x-msg URL
12/15/14 10:11:39.806 AM Mail[3223]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/15/14 10:11:39.807 AM Mail[3223]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/15/14 10:11:39.825 AM Mail[3223]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/15/14 10:11:39.825 AM Mail[3223]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/15/14 10:11:39.849 AM Mail[3223]: Could not load x-msg URL
12/15/14 10:11:40.053 AM Mail[3223]: Could not load x-msg URL
12/15/14 10:11:40.280 AM Mail[3223]: Could not load x-msg URL
12/15/14 10:11:40.288 AM Mail[3223]: Could not load x-msg URL
12/15/14 10:11:40.443 AM Mail[3223]: No worthy mechs found
12/15/14 10:11:40.684 AM Mail[3223]: No worthy mechs found
12/15/14 10:11:41.228 AM Mail[3223]: No worthy mechs found
CONSOLE DIAGNOSTIC AND USAGE MESSAGES:
I am pasting here below the report of the two crashes I got yesterday. Any thoughts are very welcome!!
------------------------------- FIRST CRASH
Process:
Mail [2189]
Path:
/Applications/Mail.app/Contents/MacOS/Mail
Identifier:
com.apple.mail
Version:
8.1 (1993)
Build Info:
Mail-1993000000000000~1
Code Type:
X86-64 (Native)
Parent Process:
??? [1]
Responsible:
Mail [2189]
User ID:
503
Date/Time:
2014-12-15 09:55:20.362 -0800
OS Version:
Mac OS X 10.10.1 (14B25)
Report Version:
11
Anonymous UUID:
(REMOVED)
Sleep/Wake UUID:
B1F8A264-AD82-49DD-90ED-5D1DE9772513
Time Awake Since Boot: 12000 seconds
Time Since Wake:
4000 seconds
Crashed Thread:
22 -[AttachmentManager _handleMessageDeleted:] Dispatch queue: NSOperationQueue 0x7fc6240e6a60 :: NSOperation 0x7fc62c1b3690 (QOS: LEGACY)
Exception Type:
EXC_BAD_ACCESS (SIGBUS)
Exception Codes:
KERN_PROTECTION_FAILURE at 0x000000015ea96fd8
VM Regions Near 0x15ea96fd8:
WebKit Malloc
000000015ea95000-000000015ea96000 [
4K] ---/rwx SM=NUL
--> STACK GUARD
000000015ea96000-000000015ea97000 [
4K] ---/rwx SM=NUL stack guard for thread 22
Stack
000000015ea97000-000000015eb19000 [ 520K] rw-/rwx SM=PRV thread 22
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib
0x00007fff9564652e mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff9564569f mach_msg + 55
2   com.apple.CoreFoundation
0x00007fff8e910b14 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation
0x00007fff8e90ffdb __CFRunLoopRun + 1371
4   com.apple.CoreFoundation
0x00007fff8e90f838 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox
0x00007fff943f843f RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox
0x00007fff943f81ba ReceiveNextEventCommon + 431
7   com.apple.HIToolbox
0x00007fff943f7ffb _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit
0x00007fff98a286d1 _DPSNextEvent + 964
9   com.apple.AppKit
0x00007fff98a27e80 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
10 com.apple.AppKit
0x00007fff98a1be23 -[NSApplication run] + 594
11 com.apple.AppKit
0x00007fff98a072d4 NSApplicationMain + 1832
12 libdyld.dylib
0x00007fff94c1a5c9 start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib
0x00007fff9564c22e kevent64 + 10
1   libdispatch.dylib
0x00007fff983caa6a _dispatch_mgr_thread + 52
Thread 2:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib
0x00007fff9564652e mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff9564569f mach_msg + 55
2   com.apple.CoreFoundation
0x00007fff8e910b14 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation
0x00007fff8e90ffdb __CFRunLoopRun + 1371
4   com.apple.CoreFoundation
0x00007fff8e90f838 CFRunLoopRunSpecific + 296
5   com.apple.CFNetwork
0x00007fff94e31d20 +[NSURLConnection(Loader) _resourceLoadLoop:] + 434
6   com.apple.Foundation
0x00007fff957fbb7a __NSThread__main__ + 1345
7   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
8   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
9   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 3:: com.apple.CFSocket.private
0   libsystem_kernel.dylib
0x00007fff9564b3f6 __select + 10
1   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
2   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
3   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 4:
0   libsystem_kernel.dylib
0x00007fff9564652e mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff9564569f mach_msg + 55
2   com.apple.CoreFoundation
0x00007fff8e910b14 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation
0x00007fff8e90ffdb __CFRunLoopRun + 1371
4   com.apple.CoreFoundation
0x00007fff8e90f838 CFRunLoopRunSpecific + 296
5   com.apple.AppKit
0x00007fff98b8b7a7 _NSEventThread + 137
6   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 5:: com.apple.CoreAnimation.render-server
0   libsystem_kernel.dylib
0x00007fff9564652e mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff9564569f mach_msg + 55
2   com.apple.QuartzCore
0x00007fff8d99dd63 CA::Render::Server::server_thread(void*) + 198
3   com.apple.QuartzCore
0x00007fff8d99dc96 thread_fun + 25
4   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
5   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
6   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 6:: JavaScriptCore::BlockFree
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a942d4 JSC::BlockAllocator::blockFreeingThreadMain() + 228
3   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
4   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
5   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
6   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 7:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 8:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 9:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 10:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 11:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 12:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 13:: JavaScriptCore::BlockFree
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a942d4 JSC::BlockAllocator::blockFreeingThreadMain() + 228
3   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
4   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
5   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
6   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 14:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 15:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 16:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 17:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 18:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 19:: JavaScriptCore::Marking
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   libc++.1.dylib
0x00007fff971ffc95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   com.apple.JavaScriptCore
0x00007fff96a9486b JSC::GCThread::waitForNextPhase() + 171
3   com.apple.JavaScriptCore
0x00007fff96a946c8 JSC::GCThread::gcThreadMain() + 88
4   com.apple.JavaScriptCore
0x00007fff96a89a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib
0x00007fff9c5732fc _pthread_body + 131
6   libsystem_pthread.dylib
0x00007fff9c573279 _pthread_start + 176
7   libsystem_pthread.dylib
0x00007fff9c5714b1 thread_start + 13
Thread 20:: -[MFIMAPAccount _fetchUnreadCountsCheckForNewMessages:] Dispatch queue: NSOperationQueue 0x7fc627a5a0b0 :: NSOperation 0x7fc6272122b0 (QOS: LEGACY)
0   libsystem_kernel.dylib
0x00007fff9564b162 __psynch_mutexwait + 10
1   com.apple.IMAP
0x00007fff93350782 -[IMAPMailboxSyncEngine _copyDataSource] + 29
2   com.apple.IMAP
0x00007fff93357fd8 -[IMAPMailboxSyncEngine _goWithMessages:] + 73
3   com.apple.Mail.framework
0x00007fff9317f827 -[MFLibraryIMAPStore _retrieveNewMessagesForCheckingNewMail:] + 423
4   com.apple.Mail.framework
0x00007fff93172a7d -[MFLibraryIMAPStore _fetchForCheckingNewMail:] + 218
5   com.apple.Mail.framework
0x00007fff93259214 -[MFRemoteStoreAccount _synchronizeMailboxesSynchronously] + 1054
6   com.apple.Mail.framework
0x00007fff931177a8 -[MFIMAPAccount _fetchUnreadCountsCheckForNewMessages:] + 1001
7   com.apple.CoreFoundation
0x00007fff8e8d933c __invoking___ + 140
8   com.apple.CoreFoundation
0x00007fff8e8d9192 -[NSInvocation invoke] + 290
9   com.apple.MailCore
0x00007fff9bfb30cc -[MCMonitoredInvocation invoke] + 242
10 com.apple.MailCore
0x00007fff9bfdd1d4 -[MCThrowingInvocationOperation main] + 48
11 com.apple.MailCore
0x00007fff9bf6571d -[_MCInvocationOperation main] + 426
12 com.apple.Foundation
0x00007fff9579b59c -[__NSOperationInternal _start:] + 653
13 com.apple.Foundation
0x00007fff9579b1a3 __NSOQSchedule_f + 184
14 libdispatch.dylib
0x00007fff983c7c13 _dispatch_client_callout + 8
15 libdispatch.dylib
0x00007fff983cb365 _dispatch_queue_drain + 1100
16 libdispatch.dylib
0x00007fff983ccecc _dispatch_queue_invoke + 202
17 libdispatch.dylib
0x00007fff983ca6b7 _dispatch_root_queue_drain + 463
18 libdispatch.dylib
0x00007fff983d8fe4 _dispatch_worker_thread3 + 91
19 libsystem_pthread.dylib
0x00007fff9c5736cb _pthread_wqthread + 729
20 libsystem_pthread.dylib
0x00007fff9c5714a1 start_wqthread + 13
Thread 21:: Dispatch queue: NSOperationQueue 0x7fc627bcedc0 :: NSOperation 0x7fc62cddc290 (QOS: LEGACY)
0   libsystem_kernel.dylib
0x00007fff9564b132 __psynch_cvwait + 10
1   com.apple.Foundation
0x00007fff957cd400 -[NSCondition waitUntilDate:] + 343
2   com.apple.IMAP
0x00007fff93341e7c -[IMAPGateway waitUntilClientOperationIsFinished:] + 370
3   com.apple.IMAP
0x00007fff93341ce5 -[IMAPGateway addClientOperation:toQueueAndWaitUntilFinished:] + 487
4   com.apple.IMAP
0x00007fff93343885 -[IMAPGateway check:] + 65
5   com.apple.Mail.framework
0x00007fff93174c31 -[MFLibraryIMAPStore _copyMessagesByID:toStore:settingFlags:newMessages:error:] + 1895
6   com.apple.Mail.framework
0x00007fff93255dc2 -[MFRemoteStore _doAppend:fromStore:error:] + 1066
7   com.apple.Mail.framework
0x00007fff932558ab -[MFRemoteStore appendMessages:unsuccessfulOnes:newMessageIDs:newMessages:newDocumentIDsByOld:f lagsToSet:forMove:error:] + 1811
8   com.apple.Mail.framework
0x00007fff93214a8b -[MFMessageStore appendMessages:unsuccessfulOnes:newMessageIDs:newMessages:flagsToSet:forMove:er ror:] + 142
9   com.apple.Mail.framework
0x00007fff93214b45 -[MFMessageStore appendMessages:unsuccessfulOnes:newMessageIDs:newMessages:flagsToSet:forMove:] + 133
10 com.apple.Mail.framework
0x00007fff93214bf6 -[MFMessageStore appendMessages:unsuccessfulOnes:newMessageIDs:newMessages:flagsToSet:] + 124
11 com.apple.Mail.framework
0x00007fff93214d2f -[MFMessageStore appendMessages:unsuccessfulOnes:newMessageIDs:newMessages:] + 103
12 com.apple.Mail.framework
0x00007fff93214da7 -[MFMessageStore appendMessages:unsuccessfulOnes:newMessageIDs:] + 74
13 com.apple.Mail.framework
0x00007fff93214e04 -[MFMessageStore appendMessages:unsuccessfulOnes:] + 53
14 com.apple.Mail.framework
0x00007fff932049da -[MFMessageRule _appendMessages:fromSourceMailbox:toDestinationMailbox:destinationStores:reject edMessages:messagesToBeDeleted:] + 880
15 com.apple.Mail.framework
0x00007fff932053c3 -[MFMessageRule performActionsOnMessages:sourceStores:destinationStores:transferredOrDeleted:re jectedMessages:messagesToBeDeleted:] + 2256
16 com.apple.Mail.framework
0x00007fff931fc3a8 routeMessagesAccordingToRule + 307
17 com.apple.Mail.framework
0x00007fff931fd331 -[MFMessageRouter routeMessages:fromStores:fetchingBodies:messagesNeedingBodies:] + 1738
18 com.apple.Mail.framework
0x00007fff9321382a -[MFMessageStore routeMessages:isUserAction:fetchingBodies:messagesNeedingBodies:] + 187
19 com.apple.Mail.framework
0x00007fff932133a1 -[MFMessageStore routeMessages:fetchingBodies:messagesNeedingBodies:] + 300
20 com.apple.IMAP
0x00007fff93359b5c -[IMAPMailboxSyncEngine _processResponsesWithMonitor:] + 3110
21 com.apple.IMAP
0x00007fff933587bc -[IMAPMailboxSyncEngine _goWithMessages:] + 2093
22 com.apple.IMAP
0x00007fff93358c79 -[IMAPMailboxSyncEngine _goWithMessagesIfNeeded:] + 61
23 com.apple.CoreFoundation
0x00007fff8e8d933c __invoking___ + 140
24 com.apple.CoreFoundation
0x00007fff8e8d9192 -[NSInvocation invoke] + 290
25 com.apple.MailCore
0x00007fff9bfb30cc -[MCMonitoredInvocation invoke] + 242
26 com.apple.MailCore
0x00007fff9bfdd1d4 -[MCThrowingInvocationOperation main] + 48
27 com.apple.MailCore
0x00007fff9bf6571d -[_MCInvocationOperation main] + 426
28 com.apple.Foundation
0x00007fff9579b59c -[__NSOperationInternal _start:] + 653
29 com.apple.Foundation
0x00007fff9579b1a3 __NSOQSchedule_f + 184
30 libdispatch.dylib
0x00007fff983c7c13 _dispatch_client_callout + 8
31 libdispatch.dylib
0x00007fff983cb365 _dispatch_queue_drain + 1100
32 libdispatch.dylib
0x00007fff983ccecc _dispatch_queue_invoke + 202
33 libdispatch.dylib
0x00007fff983ca6b7 _dispatch_root_queue_drain + 463
34 libdispatch.dylib
0x00007fff983d8fe4 _dispatch_worker_thread3 + 91
35 libsystem_pthread.dylib
0x00007fff9c5736cb _pthread_wqthread + 729
36 libsystem_pthread.dylib
0x00007fff9c5714a1 start_wqthread + 13
Thread 22 Crashed:: -[AttachmentManager _handleMessageDeleted:] Dispatch queue: NSOperationQueue 0x7fc6240e6a60 :: NSOperation 0x7fc62c1b3690 (QOS: LEGACY)
0   libsystem_malloc.dylib
0x00007fff8dea8e82 szone_malloc_should_clear + 111
1   libsystem_malloc.dylib
0x00007fff8dea8877 malloc_zone_malloc + 71
2   com.apple.CoreFoundation
0x00007fff8e8b0953 __CFStringChangeSizeMultiple + 1059
3   com.apple.CoreFoundation
0x00007fff8e8b0317 CFStringCreateMutableCopy + 519
4   com.apple.CoreFoundation
0x00007fff8e907e11 CFURLCreateStringByAddingPercentEscapes + 593
5   com.apple.Mail.framework
0x00007fff931c80b6 -[MFMailAccount _URLForInfo:] + 877
6   com.apple.Mail.framework
0x00007fff931c03ba -[MFMailAccount URLString] + 26
7   com.apple.Mail.framework
0x00007fff93149347 +[MFLibrary _getActiveAccountURLs:andActiveMailboxURLs:] + 947
8   com.apple.Mail.framework
0x00007fff9316811d +[MFLibrary executeBlock:isWriter:useTransaction:isPrivileged:] + 990
9   com.apple.Mail.framework
0x00007fff93152c6e +[MFLibrary loadSecondaryMetadataForMessage:] + 149
10 com.apple.Mail.framework
0x00007fff9318290c -[MFLibraryMessage subject] + 119
11 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
12 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasCompleteText:] + 134
13 com.apple.Mail.framework
0x00007fff9315abfe +[MFLibrary setData:forMessage:isPartial:] + 63
14 com.apple.IMAP
0x00007fff93363750 -[IMAPMessageDownload data] + 2385
15 com.apple.Mail.framework
0x00007fff9317ddbf -[MFLibraryIMAPStore _waitForDataFromDownload:uid:gateway:] + 659
16 com.apple.Mail.framework
0x00007fff9317dfd9 -[MFLibraryIMAPStore _fetchBodyDataForMessage:andHeaderDataIfReadilyAvailable:fetchIfNotAvailable:] + 429
17 com.apple.Mail.framework
0x00007fff9318c2da -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 119
18 com.apple.Mail.framework
0x00007fff9317e186 -[MFLibraryIMAPStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 117
19 com.apple.Mail.framework
0x00007fff9318c345 -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:allowPartial:] + 51
20 com.apple.Mail.framework
0x00007fff932155c5 -[MFMessageStore headerDataForMessage:fetchIfNotAvailable:allowPartial:] + 99
21 com.apple.Mail.framework
0x00007fff93215fb2 -[MFMessageStore headersForMessage:fetchIfNotAvailable:] + 102
22 com.apple.MailCore
0x00007fff9bf7306a -[MCMessage headers] + 57
23 com.apple.MailCore
0x00007fff9bf75cd6 -[MCMessage subject] + 107
24 com.apple.Mail.framework
0x00007fff93182978 -[MFLibraryMessage subject] + 227
25 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
26 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasCompleteText:] + 134
27 com.apple.Mail.framework
0x00007fff9315abfe +[MFLibrary setData:forMessage:isPartial:] + 63
28 com.apple.IMAP
0x00007fff93363750 -[IMAPMessageDownload data] + 2385
29 com.apple.Mail.framework
0x00007fff9317ddbf -[MFLibraryIMAPStore _waitForDataFromDownload:uid:gateway:] + 659
30 com.apple.Mail.framework
0x00007fff9317dfd9 -[MFLibraryIMAPStore _fetchBodyDataForMessage:andHeaderDataIfReadilyAvailable:fetchIfNotAvailable:] + 429
31 com.apple.Mail.framework
0x00007fff9318c2da -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 119
32 com.apple.Mail.framework
0x00007fff9317e186 -[MFLibraryIMAPStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 117
33 com.apple.Mail.framework
0x00007fff9318c345 -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:allowPartial:] + 51
34 com.apple.Mail.framework
0x00007fff932155c5 -[MFMessageStore headerDataForMessage:fetchIfNotAvailable:allowPartial:] + 99
35 com.apple.Mail.framework
0x00007fff93215fb2 -[MFMessageStore headersForMessage:fetchIfNotAvailable:] + 102
36 com.apple.MailCore
0x00007fff9bf7306a -[MCMessage headers] + 57
37 com.apple.MailCore
0x00007fff9bf75cd6 -[MCMessage subject] + 107
38 com.apple.Mail.framework
0x00007fff93182978 -[MFLibraryMessage subject] + 227
39 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
40 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasCompleteText:] + 134
41 com.apple.Mail.framework
0x00007fff9315abfe +[MFLibrary setData:forMessage:isPartial:] + 63
42 com.apple.IMAP
0x00007fff93363750 -[IMAPMessageDownload data] + 2385
43 com.apple.Mail.framework
0x00007fff9317ddbf -[MFLibraryIMAPStore _waitForDataFromDownload:uid:gateway:] + 659
44 com.apple.Mail.framework
0x00007fff9317dfd9 -[MFLibraryIMAPStore _fetchBodyDataForMessage:andHeaderDataIfReadilyAvailable:fetchIfNotAvailable:] + 429
45 com.apple.Mail.framework
0x00007fff9318c2da -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 119
46 com.apple.Mail.framework
0x00007fff9317e186 -[MFLibraryIMAPStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 117
47 com.apple.Mail.framework
0x00007fff9318c345 -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:allowPartial:] + 51
48 com.apple.Mail.framework
0x00007fff932155c5 -[MFMessageStore headerDataForMessage:fetchIfNotAvailable:allowPartial:] + 99
49 com.apple.Mail.framework
0x00007fff93215fb2 -[MFMessageStore headersForMessage:fetchIfNotAvailable:] + 102
50 com.apple.MailCore
0x00007fff9bf7306a -[MCMessage headers] + 57
51 com.apple.MailCore
0x00007fff9bf75cd6 -[MCMessage subject] + 107
52 com.apple.Mail.framework
0x00007fff93182978 -[MFLibraryMessage subject] + 227
53 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
54 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasCompleteText:] + 134
55 com.apple.Mail.framework
0x00007fff9315abfe +[MFLibrary setData:forMessage:isPartial:] + 63
56 com.apple.IMAP
0x00007fff93363750 -[IMAPMessageDownload data] + 2385
57 com.apple.Mail.framework
0x00007fff9317ddbf -[MFLibraryIMAPStore _waitForDataFromDownload:uid:gateway:] + 659
58 com.apple.Mail.framework
0x00007fff9317dfd9 -[MFLibraryIMAPStore _fetchBodyDataForMessage:andHeaderDataIfReadilyAvailable:fetchIfNotAvailable:] + 429
59 com.apple.Mail.framework
0x00007fff9318c2da -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 119
60 com.apple.Mail.framework
0x00007fff9317e186 -[MFLibraryIMAPStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 117
61 com.apple.Mail.framework
0x00007fff9318c345 -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:allowPartial:] + 51
62 com.apple.Mail.framework
0x00007fff932155c5 -[MFMessageStore headerDataForMessage:fetchIfNotAvailable:allowPartial:] + 99
63 com.apple.Mail.framework
0x00007fff93215fb2 -[MFMessageStore headersForMessage:fetchIfNotAvailable:] + 102
64 com.apple.MailCore
0x00007fff9bf7306a -[MCMessage headers] + 57
65 com.apple.MailCore
0x00007fff9bf75cd6 -[MCMessage subject] + 107
66 com.apple.Mail.framework
0x00007fff93182978 -[MFLibraryMessage subject] + 227
67 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
68 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasCompleteText:] + 134
69 com.apple.Mail.framework
0x00007fff9315abfe +[MFLibrary setData:forMessage:isPartial:] + 63
70 com.apple.IMAP
0x00007fff93363750 -[IMAPMessageDownload data] + 2385
71 com.apple.Mail.framework
0x00007fff9317ddbf -[MFLibraryIMAPStore _waitForDataFromDownload:uid:gateway:] + 659
72 com.apple.Mail.framework
0x00007fff9317dfd9 -[MFLibraryIMAPStore _fetchBodyDataForMessage:andHeaderDataIfReadilyAvailable:fetchIfNotAvailable:] + 429
73 com.apple.Mail.framework
0x00007fff9318c2da -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 119
74 com.apple.Mail.framework
0x00007fff9317e186 -[MFLibraryIMAPStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 117
75 com.apple.Mail.framework
0x00007fff9318c345 -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:allowPartial:] + 51
76 com.apple.Mail.framework
0x00007fff932155c5 -[MFMessageStore headerDataForMessage:fetchIfNotAvailable:allowPartial:] + 99
77 com.apple.Mail.framework
0x00007fff93215fb2 -[MFMessageStore headersForMessage:fetchIfNotAvailable:] + 102
78 com.apple.MailCore
0x00007fff9bf7306a -[MCMessage headers] + 57
79 com.apple.MailCore
0x00007fff9bf75cd6 -[MCMessage subject] + 107
80 com.apple.Mail.framework
0x00007fff93182978 -[MFLibraryMessage subject] + 227
81 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
82 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasCompleteText:] + 134
83 com.apple.Mail.framework
0x00007fff9315abfe +[MFLibrary setData:forMessage:isPartial:] + 63
84 com.apple.IMAP
0x00007fff93363750 -[IMAPMessageDownload data] + 2385
85 com.apple.Mail.framework
0x00007fff9317ddbf -[MFLibraryIMAPStore _waitForDataFromDownload:uid:gateway:] + 659
86 com.apple.Mail.framework
0x00007fff9317dfd9 -[MFLibraryIMAPStore _fetchBodyDataForMessage:andHeaderDataIfReadilyAvailable:fetchIfNotAvailable:] + 429
87 com.apple.Mail.framework
0x00007fff9318c2da -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 119
88 com.apple.Mail.framework
0x00007fff9317e186 -[MFLibraryIMAPStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 117
89 com.apple.Mail.framework
0x00007fff9318c345 -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:allowPartial:] + 51
90 com.apple.Mail.framework
0x00007fff932155c5 -[MFMessageStore headerDataForMessage:fetchIfNotAvailable:allowPartial:] + 99
91 com.apple.Mail.framework
0x00007fff93215fb2 -[MFMessageStore headersForMessage:fetchIfNotAvailable:] + 102
92 com.apple.MailCore
0x00007fff9bf7306a -[MCMessage headers] + 57
93 com.apple.MailCore
0x00007fff9bf75cd6 -[MCMessage subject] + 107
94 com.apple.Mail.framework
0x00007fff93182978 -[MFLibraryMessage subject] + 227
95 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
96 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasCompleteText:] + 134
97 com.apple.Mail.framework
0x00007fff9315abfe +[MFLibrary setData:forMessage:isPartial:] + 63
98 com.apple.IMAP
0x00007fff93363750 -[IMAPMessageDownload data] + 2385
99 com.apple.Mail.framework
0x00007fff9317ddbf -[MFLibraryIMAPStore _waitForDataFromDownload:uid:gateway:] + 659
100 com.apple.Mail.framework
0x00007fff9317dfd9 -[MFLibraryIMAPStore _fetchBodyDataForMessage:andHeaderDataIfReadilyAvailable:fetchIfNotAvailable:] + 429
101 com.apple.Mail.framework
0x00007fff9318c2da -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 119
102 com.apple.Mail.framework
0x00007fff9317e186 -[MFLibraryIMAPStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 117
103 com.apple.Mail.framework
0x00007fff9318c345 -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:allowPartial:] + 51
104 com.apple.Mail.framework
0x00007fff932155c5 -[MFMessageStore headerDataForMessage:fetchIfNotAvailable:allowPartial:] + 99
105 com.apple.Mail.framework
0x00007fff93215fb2 -[MFMessageStore headersForMessage:fetchIfNotAvailable:] + 102
106 com.apple.MailCore
0x00007fff9bf7306a -[MCMessage headers] + 57
107 com.apple.MailCore
0x00007fff9bf75cd6 -[MCMessage subject] + 107
108 com.apple.Mail.framework
0x00007fff93182978 -[MFLibraryMessage subject] + 227
109 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
110 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasCompleteText:] + 134
111 com.apple.Mail.framework
0x00007fff9315abfe +[MFLibrary setData:forMessage:isPartial:] + 63
112 com.apple.IMAP
0x00007fff93363750 -[IMAPMessageDownload data] + 2385
113 com.apple.Mail.framework
0x00007fff9317ddbf -[MFLibraryIMAPStore _waitForDataFromDownload:uid:gateway:] + 659
114 com.apple.Mail.framework
0x00007fff9317dfd9 -[MFLibraryIMAPStore _fetchBodyDataForMessage:andHeaderDataIfReadilyAvailable:fetchIfNotAvailable:] + 429
115 com.apple.Mail.framework
0x00007fff9318c2da -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 119
116 com.apple.Mail.framework
0x00007fff9317e186 -[MFLibraryIMAPStore _fetchHeaderDataForMessage:fetchIfNotAvailable:] + 117
117 com.apple.Mail.framework
0x00007fff9318c345 -[MFLibraryStore _fetchHeaderDataForMessage:fetchIfNotAvailable:allowPartial:] + 51
118 com.apple.Mail.framework
0x00007fff932155c5 -[MFMessageStore headerDataForMessage:fetchIfNotAvailable:allowPartial:] + 99
119 com.apple.Mail.framework
0x00007fff93215fb2 -[MFMessageStore headersForMessage:fetchIfNotAvailable:] + 102
120 com.apple.MailCore
0x00007fff9bf7306a -[MCMessage headers] + 57
121 com.apple.MailCore
0x00007fff9bf75cd6 -[MCMessage subject] + 107
122 com.apple.Mail.framework
0x00007fff93182978 -[MFLibraryMessage subject] + 227
123 com.apple.Mail.framework
0x00007fff9316e38d -[_MFDataCollector setData:] + 303
124 com.apple.Mail.framework
0x00007fff9315ac95 +[MFLibrary setData:forMessage:isPartial:hasComp

Slow delete

Similar Messages

Maybe you are looking for