title: Android emulator gets killed
body: <p>I've seen this question: <a href="https://stackoverflow.com/questions/37281365/emulator-not-running-on-android-studio">Emulator Not Running on Android Studio</a> but I don't have Docker installed.</p>
  
  <p>There's very little code in my program (it's just a single panel with a few buttons w/o any code attached to them).</p>
  
  <p>I'm running this on Ubuntu 14 LTS.</p>
  
  <p>The symptoms are these: The emulator starts, I see the word "android" appear on its screen, and then the window with the emulator closes, and the text</p>
  
  <blockquote>
    <p>Error while waiting for device: The emulator process for AVD Nexus_5_API_25 was killed.</p>
  </blockquote>
  
  <p>appears in <code>Run</code> console output.  No other useful information is printed anywhere.</p>
  
  <p>In the console output of Android Studio I see this:</p>
  
  <pre><code>[ 145948]   WARN - run.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null 
  ... repeated multiple times ...
  [ 147039]   WARN - run.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null 
  *** Error in `/home/wvxvw/projects/android-sdk/tools/qemu/linux-x86_64/qemu-system-i386': double free or corruption (fasttop): 0x00007fe070a0d760 ***
  </code></pre>
  
  <hr>
  
  <p>After trying different processor architectures in combination with phone models and other setting + disabling my desktop theme (apparently, this is a serious issue for Google developers: <a href="https://code.google.com/p/android/issues/detail?id=66748" rel="nofollow noreferrer">https://code.google.com/p/android/issues/detail?id=66748</a> ), I could find some configuration in which the emulator can actually launch (it takes it about five minutes to do so, but hey, it's still better than nothing, right?) And then I could connect to this running emulator from Android studio (it cannot launch it though on its own).</p>