Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

MailMate very slow performance when expunging messages

#597

I have a smart folder that contains ~8k messages. When I select all and Opt-Delete to expunge them, it takes far far longer than I would expect. It's currently been going about 4 minutes and there are 6600 left.

I would expect this operation to complete in a number of seconds (a minute would be a really long time). My fans are spinning up and the process consumes all of the CPU during this time.

Do you agree it's something that should complete much quicker than I'm observing?

Reported by nall · January 20th, 2014 @ 10:45 PM

State: new
Milestone: none
Assigned to: benny benny

Activity

  1. benny
    benny

    Yes, it should be quicker, but it's not something I've tried myself recently. The slowest part should be deleting the messages from the database indexes. You can sample the process to give me an idea of what is slow. You can do this using the Activity Monitor in /Applications/Utilities/.

    January 20th, 2014 @ 11:24 PM

  2. nall
    nall

    Attaching the sample during a slow one.

        +       !       :       1300 __CFRunLoopRun  (in CoreFoundation) + 974  [0x95d0a39e]
    +       !       :         1300 __CFRunLoopDoObservers  (in CoreFoundation) + 399  [0x95d194ef]
    +       !       :           1300 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__  (in CoreFoundation) + 30  [0x95d1959e]
    +       !       :             1300 _runLoopObserverWithBlockContext  (in CoreFoundation) + 29  [0x95d19b4d]
    +       !       :               1002 __35-[NSWindow _postInvalidCursorRects]_block_invoke3075  (in AppKit) + 54  [0x9893a307]
    +       !       :               | 1002 _handleInvalidCursorRectsNote  (in AppKit) + 1087  [0x982c2e64]
    +       !       :               |   995 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 1665  [0x9826afe2]
    +       !       :               |   + 995 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 1665  [0x9826afe2]
    +       !       :               |   +   995 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 1665  [0x9826afe2]
    +       !       :               |   +     995 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 1665  [0x9826afe2]
    +       !       :               |   +       995 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 1665  [0x9826afe2]
    +       !       :               |   +         995 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 1665  [0x9826afe2]
    +       !       :               |   +           995 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 1665  [0x9826afe2]
    +       !       :               |   +             993 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 1665  [0x9826afe2]
    +       !       :               |   +             ! 990 -[NSView(NSInternal) _updateTrackingAreas]  (in AppKit) + 749  [0x9826ac4e]
    +       !       :               |   +             ! : 977 -[NSView(NSInternal) _uninstallRemovedTrackingAreas]  (in AppKit) + 545  [0x9815ae1c]
    +       !       :               |   +             ! : | 969 -[NSView(NSInternal) _uninstallTrackingArea:]  (in AppKit) + 75  [0x982608ff]
    +       !       :               |   +             ! : | + 968 -[NSWindow _discardTrackingRect:]  (in AppKit) + 167  [0x98260ac1]
    +       !       :               |   +             ! : | + ! 968 -[NSWindow _removeTrackingRect:]  (in AppKit) + 24  [0x982c0b78]
    +       !       :               |   +             ! : | + !   968 _NSClearTrackingRect  (in AppKit) + 48  [0x982c0bad]
    +       !       :               |   +             ! : | + !     967 _NXClearTrackingRect  (in AppKit) + 67  [0x982c0bf7]
    +       !       :               |   +             ! : | + !     : 966 CGSRemoveTrackingArea  (in CoreGraphics) + 78  [0x97a0c87c]
    +       !       :               |   +             ! : | + !     : | 965 _CGSRemoveTrackingArea  (in CoreGraphics) + 133  [0x97a0c941]
    +       !       :               |   +             ! : | + !     : | + 963 mach_msg  (in libsystem_kernel.dylib) + 68  [0x9c24716c]
    +       !       :               |   +             ! : | + !     : | + ! 963 mach_msg_trap  (in libsystem_kernel.dylib) + 10  [0x9c247f7a]
    +       !       :               |   +             ! : | + !     : | + 2 mach_msg  (in libsystem_kernel.dylib) + 284,68  [0x9c247244,0x9c24716c]
    +       !       :               |   +             ! : | + !     : | 1 _CGSRemoveTrackingArea  (in CoreGraphics) + 133  [0x97a0c941]

    January 20th, 2014 @ 11:49 PM

  3. benny
    benny

    Thanks. It looks like MailMate is spending its time updating the GUI. I'll see if I can reproduce this issue.

    Did it eventually complete the action without problems?

    January 21st, 2014 @ 08:24 AM

  4. nall
    nall

    Yes, eventually it completes. Even after I 'Force Quit' MailMate the messages were red upon restarting and eventually were removed.

    January 21st, 2014 @ 04:51 PM

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.