title: Android emulator start makes Mac unresponsive
body: <p>I'm trying to set up an android emulator on a brand new MacBook Pro (2019 late i7 6-core (Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz), Radeon 555x). </p>
  
  <p>When I set up an emulator always happens the same: Emulator starts to boot and mac become unresponsive (trackpad becomes a brick. Then the Mac system restarts with no error report just with "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available" message.</p>
  
  <p>What I tried: Reinstall HAXM, different versions of HAXM, different versions of the android studio (inc. 4.0.1 canary), different versions of AVD, all above using homebrew, using software graphic, more RAM, and clean iOS reinstall too (with full clear). Genymotion also failed.
  On Windows, after a clean install (boot camp) the same happens. ARM-based emulators can start, but they are extremely slow.</p>
  
  <p>I've reset SMC, NVRAM and diagnostics say everything is fine...</p>
  
  <p>All suggestion is appreciated.</p>
  
  <p>Updates:
  Current MacOS version: 10.15.3 (19D76)</p>
  
  <p>I also tried backing up the <strong>wrong</strong> mac and restore on another MBP, in this case, it worked on the other MBP.
  I tried to remove these folders one by one: </p>
  
  <pre><code>• ~/Library/InputMethods
    • ~/Library/InputManagers
    • ~/Library/Caches
    • ~/Library/Containers
    • ~/Library/Application Support
    • ~/Library/Preferences
    • /Library/LaunchAgents
    • /Library/LaunchDaemons
    • /Library/StartupItems
    • /Library/InputMethods
    • /Library/InputManagers
  </code></pre>
  
  <ul>
  <li>Tried in safe mode, </li>
  <li>with other emulators (genymotion, bluestacks),</li>
  <li>under a virtual machine (VMware and VirtualBox with ubuntu) when
  the emulator starts the same happens.</li>
  <li>tired under Catalina</li>
  <li>Contacted intel, they said: "Apple has explicitly requested all support inquiries or issues to be addressed directly to them"</li>
  <li>Contacted Apple (million times... for 6 months) they said: "Since the problem is caused by a third party application, there is limited protection or support to provide." After using capture data, their engineers have found out that the issue may be caused by "com.intel.haxm" (like I said, surprise!)</li>
  </ul>