IssueTracker

Today I updated several SDK components.  I'm on the stable channel, and before today I was up to date for the stable channel.  The one I believe I'm having the trouble with is the 29.0.0 platform tools.  If I go back to 28.0.2, everything is fine.

When I start the Emulator (via Android Studio), I get a Windows "adb.exe has stopped working" check for solution/close program dialog.  Then a couple of seconds later I get another, and another.  The emulator does come up, and it's GUI is responsive, but I can't really access it from Android Studio.  The stream of Windows error dialogs continues until I stop the emulator.

I can access a real test device just fine.

When I change my "platform-tools" folder back to the previous version, which I believe was 28.0.2, everything works fine.  This is the workaround I'm planning on using.

I've tried this with both an AVD that I had before the update to 29.0.0 and one I created after the update.  It acts the same.

I have not tried to run the emulator from the command line.

This part I can not reliably reproduce, but I've seen it several times.  Sometimes, I get an error dialog after I start the emulator (via Android Studio) but before the first adb.exe crash dialog.  That error dialog says something about my adb.exe being hopelessly out of date.  I'm not sure who is generating that dialog, but I don't think it's Windows.  Over the years I think I've seen that same error very intermittently, but ignoring  it never seems to have any negative conciquences.

 Since I'm not seeing too much yelling and screaming about this on the net I'm assuming I'm in a relatively small group.  Windows 8.1 for one.  My most non-standard thing I can think of about my system is that the android SDK folder and the android AVD folder are both on my E: drive (C: is the system drive and where my hold folder is).  This is not new.

I have a very low-end Windows 10 machine that I only use in emergencies and it seems to be working fine.


Please Read:
https://developer.android.com/studio/report-bugs.html#emulator-bugs

Android Studio Version: 3.4.0-2

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 29.0.11-5598178
HAXM / KVM Version: HAXM 7.5.1

Android SDK Tools: 26.1.1

Host Operating System: Windows 8.1

CPU Manufacturer: Intel CPU
Virtualization is supported
64-bit CPU

RAM: 16316 MB

GPU: GPU #1
  Make: 10de
  Model: NVIDIA GeForce 840M
  Device ID: 1341


Build Fingerprint: google/sdk_gphone_x86/generic_x86:8.1.0/OSM1.180201.031/5455776:userdebug/dev-keys

AVD Details: Name: Nexus_5X_API_27_8.1_x86_Google_APIs_
CPU/ABI: x86
Path: E:\LeeExtra\Dev\.android\avd\Nexus_5X_API_27_8.1_x86_Google_APIs_.avd
Target: google_apis [Google APIs] (API level 27)
Skin: nexus_5x
SD Card: 512M
AvdId: Nexus_5X_API_27_8.1_x86_Google_APIs_
PlayStore.enabled: false
avd.ini.displayname: Nexus 5X API 27 (8.1 x86 Google APIs)
avd.ini.encoding: UTF-8
disk.dataPartition.size: 800M
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: emulated
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:ae200ad6786ec467cb9067f7b46b0fd1
hw.device.manufacturer: Google
hw.device.name: Nexus 5X
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 420
hw.lcd.height: 1920
hw.lcd.width: 1080
hw.mainKeys: no
hw.ramSi