Adobe Bridge CC 2015 Crashing on Mac OSX 10.11.6 with dual monitors setup

Version 1

    Hello Forum members,


    Since many members have been posting issues regarding Adobe Bridge CC 2015 crashing on Mac OSX 10.11.6, we are creating this document providing a workaround and the reason why this issue still persists on El Capitan.


    If you are using Adobe Bridge CC 2015 on a dual monitor setup and it crashes during launch or browsing folders, please try to check the crash thread mentioned in the crash report.


    "Thread 0 Crashed:: Dispatch queue:

    0   libobjc.A.dylib               0x00007fff8c4ea16f objc_release + 31

    1       0x00007fff82a83c12 _CFAutoreleasePoolPop + 50

    2           0x00007fff9358b9ea -[NSAutoreleasePool drain] + 153

    3               0x00007fff95807e53 -[NSApplication run] + 893

    4   com.adobe.bridge6.3           0x000000010c311247 0x10be8b000 + 4743751

    5   com.adobe.bridge6.3           0x000000010c30a029 0x10be8b000 + 4714537

    6   com.adobe.bridge6.3           0x000000010c30a0fd 0x10be8b000 + 4714749

    7   com.adobe.bridge6.3           0x000000010c3ed310 0x10be8b000 + 5645072

    8   com.adobe.bridge6.3           0x000000010c3eda95 0x10be8b000 + 5646997

    9   libdyld.dylib                 0x00007fff88c505ad start + 1”


    We are not expecting from our customers to analyze crash reports, however if you look at the highlighted keywords it would help you in identifying the issue and act accordingly. If the crash thread consists of the keywords highlighted above, please try the workaround mentioned below.


    Workaround: Click on the apple icon and choose system preferences. Click on mission control and uncheck the option "Displays have separate spaces". Restart the                          machine and try to launch Bridge CC 2015 again and check if the issue persists. Please refer to the below article for more information.

                           (Adobe Bridge CC crashes on Mac OS X with dual monitors )


    mission control.jpg


    I understand this is a workaround and not a solution and might impact your workflow, however as of now we do not have any other solution.


    Many of you have asked this question, why has this issue still not resolved on Mac OS 10.11.


    As we have investigated so far, this issue is specific to Mac OSX 10.11.6; this upgrade was available on 18th July.


    While our testing on MAC OSX 10.11.6 BETA, the issue was not replicable.


    We are working towards the fix and appreciate your patience.