Unable to run GMD devices, no reason given [258157541]

Bug

Status Update

No update yet.

Description

wk...@google.com

created issue #1

Nov 8, 2022 10:20AM

I am unable to run any GMD device. Previously I've seen a generic error message on any device configuration I tried, that said something about trying to run the emulator in Studio to verify it works (I verified I can run emulators in Studio), but it didn't help me solve my issue. I started deleting various folders with downloaded or created emulators to see if I can get back to a working state, but now my GMD setup task just hangs forever with the following info:

Using local directory build cache for the root build (location = /home/wkal/.gradle/caches/build-cache-1, removeUnusedEntriesAfter = 7 days).
Now considering [/home/wkal/AndroidStudioProjects/nowinandroid/build-logic, /home/wkal/AndroidStudioProjects/nowinandroid] as hierarchies to watch
Projects loaded. Root project using build file '/home/wkal/AndroidStudioProjects/nowinandroid/build.gradle.kts'.
Included projects: [root project 'nowinandroid', project ':benchmark']
Tasks to be executed: [task ':benchmark:AospAtd30Setup']
Tasks that were excluded: []
Resolve mutations for :benchmark:AospAtd30Setup (Thread[included builds Thread 2,5,main]) started.
Resolve mutations for :benchmark:AospAtd30Setup (Thread[included builds Thread 2,5,main]) completed. Took 0.0 secs.
:benchmark:AospAtd30Setup (Thread[Execution worker,5,main]) started.
INFO    | Android emulator version 32.1.5.0 (build_id 9192776) (CL:N/A)
INFO    | Found systemPath /home/wkal/Android/Sdk/system-images/android-31/default/x86_64/
INFO    | Crashreporting disabled, not reporting crashes.
INFO    | Duplicate loglines will be removed, if you wish to see each indiviudal line launch with the -log-nofilter flag.
INFO    | added library /home/wkal/Android/Sdk/emulator/lib64/vulkan/libvulkan.so

> Task :benchmark:AospAtd30Setup
Caching disabled for task ':benchmark:AospAtd30Setup' because:
  Caching has been disabled for the task
Task ':benchmark:AospAtd30Setup' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
Device: dev31_default_x86_64_Pixel_2 already exists. AVD creation skipped.
Checking default_boot on device dev31_default_x86_64_Pixel_2 is loadable.
<-------------> 0% EXECUTING [2m 41s]
> :benchmark:AospAtd30Setup

It never progressess or fails.

How can I help debug this?
Can we provide more useful messages on reasons why GMD is unable to start?

Build: AI-222.4345.14.2221.9252092, 202211031339, 

AI-222.4345.14.2221.9252092, JRE 17.0.4.1+0-17.0.4.1b469.62-9127311x64 JetBrains s.r.o., OS Linux(amd64) v5.18.16-1rodete4-amd64, screens 2048.0x1152.0

AS: Flamingo | 2022.2.1 Canary 8
Kotlin plugin: 222-1.7.20-release-AS3739.54
Android Gradle Plugin: 7.3.1
Gradle: 7.5.1
Gradle JDK: JetBrains Runtime version 17.0.4
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: (not found)


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

Comments

wk...@google.com <wk...@google.com> #2Nov 8, 2022 10:27AM

I tried adding screenshotTestImplementation(libs.androidx.window) but it didn't fix it.

debug.txt

60 KB

View

Download

jv...@google.com <jv...@google.com> Nov 9, 2022 03:39PM

Assigned to an...@google.com.

hu...@google.com <hu...@google.com> #3Dec 6, 2022 11:14PM

Reassigned to wk...@google.com.

This is likely a duplicate of b/388773416. Could you try adding libs.androidx.window dependency to implementation to see if it works?

wk...@google.com <wk...@google.com> #4Dec 7, 2022 10:24AM

Reassigned to hu...@google.com.

So I seem to have two different problems, but maybe they're connected:

On API 31 the Gradle task never finishes and I have to CTRL-C

On API 30 I always get an exception

Both logs attached with kernel logging enabled

Message last modified on Dec 7, 2022 10:24AM

debug-31-hang.txt

117 KB

View

Download

debug-30-crash2.txt

86 KB

View

Download

hu...@google.com <hu...@google.com> #5Dec 7, 2022 06:49PM

Reassigned to ya...@google.com.

I couldn't find any interesting line from debug-31-hang.txt. debug-30-crash2.txt has an interesting error:

X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  149 ()
  Minor opcode of failed request:  7
  Serial number of failed request:  57
  Current serial number in output stream:  58

Yahan, have you seen this error message from an emulator's kernel log output?

hu...@google.com <hu...@google.com> #6Dec 7, 2022 06:56PM

In a meanwhile, could you also try using those flags: -Pandroid.testoptions.manageddevices.emulator.gpu="swiftshader_indirect" and -Dorg.gradle.workers.max=1?

ya...@google.com <ya...@google.com> #7Dec 7, 2022 06:58PM

Reassigned to wk...@google.com.

Re #5 I don't remember seeing this error message.

I was expecting a much longer emulator log if it launches successfully. Would you try it with the swiftshader flag first? (as instructed in #6)

Also, would you try to create an AVD in Android Studio with the AOSP ATD image, then launch the emulator from command line with the "-no-window" flag? Your command should look like:

/path/to/emulator -avd your_avd_name -no-window

The emulator should have no pop up window, but it will print a "Boot complete" message in the console after a while.

wk...@google.com <wk...@google.com> #8Dec 8, 2022 09:56AM

both API 30 and 31 setup task completed successfully for me with just -Pandroid.testoptions.manageddevices.emulator.gpu=swiftshader_indirect

to...@googlemail.com <to...@googlemail.com> #9Jan 24, 2023 09:57AM

Setting the graphic acceleration to "swiftshader_indirect" works for me (when run on my Desktop machine), too. https://developer.android.com/studio/run/emulator-acceleration#command-gpu

Message last modified on Mar 6, 2023 10:31AM

is...@google.com <is...@google.com> Jul 7, 2023 12:08PM

Status: New

Issue 258157541

Description

Issue summary

Comments

wk...@google.com <wk...@google.com> #2Nov 8, 2022 10:27AM

jv...@google.com <jv...@google.com> Nov 9, 2022 03:39PM

hu...@google.com <hu...@google.com> #3Dec 6, 2022 11:14PM

wk...@google.com <wk...@google.com> #4Dec 7, 2022 10:24AM

hu...@google.com <hu...@google.com> #5Dec 7, 2022 06:49PM

hu...@google.com <hu...@google.com> #6Dec 7, 2022 06:56PM

ya...@google.com <ya...@google.com> #7Dec 7, 2022 06:58PM

wk...@google.com <wk...@google.com> #8Dec 8, 2022 09:56AM

to...@googlemail.com <to...@googlemail.com> #9Jan 24, 2023 09:57AM

is...@google.com <is...@google.com> Jul 7, 2023 12:08PM

Add comment

Issue metadata