Wiping out AVD fails while emulator is slowly stopping [249151943]

Fixed

Bug

Status Update

No update yet.

Description

ch...@google.com

created issue #1

Sep 26, 2022 09:29PM

I needed to wipe data on one of my emulators. When I tried this, it said I needed to close the emulator instance (see attached screenshot).
I clicked the close button on the emulator window, but this didn't fix it (even though the device window now says "No running emulators"). I can't figure out how I am supposed to close it; there is nothing obvious in the UI or menus.

At the very least, the dialog in the screenshot should give some hint how we are supposed to perform that task.

Build: AI-213.7172.25.2113.9014738, 202208312042,

AI-213.7172.25.2113.9014738, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Mac OS X(x86_64) v12.6, screens 5120.0x2880.0; Retina

AS: Dolphin | 2021.3.1
Kotlin plugin: 213-1.7.10-release-for-android-studio-AS6777.52
Android Gradle Plugin: 7.3.0
Gradle: 7.4
Gradle JDK: Amazon Corretto version 11.0.9
NDK: from local.properties: (not specified), latest from SDK: 23.1.7779620
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)

IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Mon Sep 26 2022 14:27:47 GMT-0700 (Pacific Daylight Time).png

40 KB

View

Download

Comments

ru...@google.com <ru...@google.com> Sep 26, 2022 09:32PM

Assigned to an...@google.com.

sp...@google.com <sp...@google.com> #2Sep 26, 2022 09:39PM

Reassigned to ch...@google.com.

To the reporter: this error is related to the class NotificationsViewModel. I'm trying to figure out exactly how this could happen, but haven't quite gotten there yet. The error seems to imply that the class's constructor is marked with @AssistedInject, but potentially also with @Inject (even though that wouldn't build).

Would you mind sharing some details about how exactly this view model is using Dagger attributes?

(I have a potential fix I can make regardless, but it's always helpful to actually understand the root cause.)

ch...@google.com <ch...@google.com> #3Sep 26, 2022 09:46PM

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 Narwhal | 2025.1.1 Canary 3
Android Gradle Plugin 8.11.0-alpha03

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!

ch...@google.com <ch...@google.com> #4Sep 26, 2022 09:46PM

screenshot:

Mon Sep 26 2022 14:46:52 GMT-0700 (Pacific Daylight Time).png

26 KB

View

Download

ch...@google.com <ch...@google.com> #5Sep 26, 2022 09:52PM

Note that clicking on the Play button (for a running emulator instance) does nothing. It does launch an emulator if that device is not currently running, but it does nothing (like stopping it) if it's already running

sp...@google.com <sp...@google.com> #6Sep 26, 2022 09:54PM

Reassigned to ju...@google.com.

Emulator shutdown does take a while, primarily due to saving of a snapshot.

Studio could probably remember that it asked emulator to stop and forcefully kill it, if it is still running, when it tries to wipe out the AVD.

sp...@google.com <sp...@google.com> #7Sep 26, 2022 10:09PM

Re #5

This may have improved in Electric Eel and/or Flamingo.

ju...@google.com <ju...@google.com> Oct 20, 2022 06:19PM

Reassigned to ha...@google.com.

sp...@google.com <sp...@google.com> #8Feb 14, 2023 11:58PM

The emulator state may be queried by the adb emu avd status console command that returns "virtual device is stopped" if the emulator is shutting down, or "virtual device is running" otherwise.

sp...@google.com <sp...@google.com> Mar 25, 2025 04:21PM

Accepted by sp...@google.com.

sp...@google.com <sp...@google.com> Mar 25, 2025 11:28PM

Marked as fixed.

an...@google.com <an...@google.com> #9Mar 27, 2025 06:02PM