title: Android Studio crashes on Mac OS El Capitan randomly, when ADB is initialized
body: <p>I am using newest version of Android Studio (2.0.0-beta5) and I am observing very strange behavior. If I turn on ADB from within Android Studio (no matter for what purpose - seeing logs, debugging or installing app) Android Studio crashes repeateadely.</p>
  
  <p>So far I found only one solution to that problem, which is quite unsatisfying: making it impossible for AS to localize adb (I achieve that by moving adb from platform-tools to any other localization.</p>
  
  <p>I have already tried:<br>
  1. Updating java (I have version 1.8.0_74-b02) but happened on earlier versions as well (for at least u71)<br>
  2. Downgrading Android Studio (to latest stable version - 1.5.0)<br>
  3. Running different devices connected to adb. Haven't tried with no device connected so far.<br></p>
  
  <p>Here is what log happens everytime before crash (from ~/Library/Logs/AndroidStudioXX.X/</p>
  
  <pre><code>2016-02-18 16:02:07,374 [1025648]   INFO -                 #com.android.ddmlib - Opening a debugger listener at port 8602 for client with pid 1789 
  2016-02-18 16:02:07,374 [1025648]   WARN -            #com.android.ddmlib - Broken pipe
  java.io.IOException: Broken pipe
  at sun.nio.ch.FileDispatcher.write0(Native Method)
  at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
  at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:69)
  at sun.nio.ch.IOUtil.write(IOUtil.java:40)
  at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:336)
  at com.android.ddmlib.JdwpPacket.write(JdwpPacket.java:179)
  at com.android.ddmlib.Client.send(Client.java:654)
  at com.android.ddmlib.jdwp.JdwpAgent.send(JdwpAgent.java:92)
  at com.android.ddmlib.HandleHeap.sendREAQ(HandleHeap.java:349)
  at com.android.ddmlib.Client.requestAllocationStatus(Client.java:517)
  at com.android.ddmlib.DeviceMonitor.createClient(DeviceMonitor.java:573)
  at com.android.ddmlib.DeviceMonitor.openClient(DeviceMonitor.java:545)
  at com.android.ddmlib.DeviceMonitor.processIncomingJdwpData(DeviceMonitor.java:507)
  at com.android.ddmlib.DeviceMonitor.deviceClientMonitorLoop(DeviceMonitor.java:403)
  at com.android.ddmlib.DeviceMonitor.access$100(DeviceMonitor.java:65)
  at com.android.ddmlib.DeviceMonitor$1.run(DeviceMonitor.java:326)
  </code></pre>
  
  <p>Here is where I figured out it might be connected with adb, so decided to disable it.</p>
  
  <p>Will appreciate any help, since it makes my work really difficult.</p>
  
  <p>EDIT:</p>
  
  <p>After clean installation of latest stable version (1.5.1) error still occurs. The difference is, that I cannot see any logs, seems like there is a black hole in them, starting few minutes before crash. Pasting MacOs problem report which displays directly after crash.</p>
  
  <pre><code>System Integrity Protection: enabled
  
  Crashed Thread:        0  Dispatch queue: com.apple.main-thread
  
  Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
  Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000020
  Exception Note:        EXC_CORPSE_NOTIFY
  
  VM Regions Near 0x20:
  --&gt; 
      __TEXT                 0000000100000000-000000010000b000 [   44K]     r-x/rwx SM=COW  /Applications/Android Studio.app/Contents/MacOS/studio
  
  Application Specific Information:
  Java information:
  Exception type: Bus Error (0xa) at pc=7fffa174f103
  
   Java VM: Java HotSpot(TM) 64-Bit Server VM (20.65-b04-468 mixed mode      macosx-amd64)
  
  Current thread (1070d5800):  JavaThread "AWT-AppKit" daemon [_thread_in_native, id=2116415488, stack(7fff5f400000,7fff5fc00000)]
  Stack: [7fff5f400000,7fff5fc00000]
  </code></pre>
  
  <p>I also tried limiting myself to one instance of AS and disabling all other apps that might use adb (like Vysor). No result...</p>