Locations sent to one emulator are sent to all of them [73450633]

Fixed

Bug

Status Update

No update yet.

Description

bo...@gmail.com

created issue #1

Feb 16, 2018 05:51PM

Android Studio Version:

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 27.1.7-4581633

HAXM / KVM Version: HVF 10.13.0

Android SDK Tools: 26.1.1

Host Operating System: Mac OS X 10.13.3

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

Steps to Reproduce Bug:
- Open 2 emulators
- In one of them, send a location, using Extended controls / Location

Expected Behavior:
The location should be sent only to the emulator that was used.

Observed Behavior:
The location is sent to both emulators.

Because of this, tests involving two people interacting at two different locations are almost impossible to do.

Comments

lf...@google.com <lf...@google.com> Feb 17, 2018 12:13AM

Assigned to lf...@google.com.

lf...@google.com <lf...@google.com> #2Feb 18, 2018 03:48AM

Adding 2 more thread dumps from another freeze. Again after switching branches and updating from git.

ap...@google.com <ap...@google.com> #3Feb 20, 2018 09:36PM

Thanks for the report. I believe that this is fixed in our development branch, and also in the branch that will become Ladybug Feature Drop Beta. If you could verify that this doesn't happen in a nightly build (from https://developer.android.com/studio/nightly) that would be helpful -- and of course if you can trigger this in a recent nightly build, that's would be very important information.

ap...@google.com <ap...@google.com> #4Feb 20, 2018 09:41PM

Sorry, I have not tried it on the nightly build, but since then I updated to Meerkat and I have not seen the freeze afterwards.

pj...@google.com <pj...@google.com> Feb 21, 2018 06:25PM

Marked as fixed.

lf...@google.com <lf...@google.com> #5Feb 21, 2018 06:39PM

That's good to hear. I think that the fix (which for reference was https://github.com/JetBrains/intellij-community/commit/fe621544dd61a9af34d97958d3d823a7c3454a87) is effective for both beta and canary branches.

For the record I am also arranging for https://github.com/JetBrains/intellij-community/commit/a444c8a500883669fc05c7177f93b5b794fdd13b (same fix, different implementation class) to be included; it's probably inactive code in our configurations, but it might be possible to trigger nevertheless.

Thanks for the confirmation!

lf...@google.com <lf...@google.com> #6Feb 24, 2018 06:14AM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Ladybug Feature Drop | 2024.2.2 RC 1
Android Gradle Plugin 8.8.0-rc01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!