•  
    Also have this issue on a large session,

    Running a test bed using Mavericks 10.9.3 (13D12) so suspect this is due to an Apple update?
    jhourihane 1 year ago