Starting Chrome crashes Emulator on x86_64 [225541819]

Fixed

Bug

NeedsInfo

Status Update

No update yet.

Description

jb...@gtempaccount.com

created issue #1

Mar 21, 2022 01:34PM

DESCRIBE THE ISSUE IN DETAIL:

STEPS TO REPRODUCE:

Start AVD
Start the Chrome App

See Screenshot as attachement

Log:

$ emulator -avd Pixel_5_API_28 
INFO    | Android emulator version 31.2.8.0 (build_id 8143646) (CL:N/A)
Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
INFO    | configAndStartRenderer: setting vsync to 60 hz
WARNING | cannot add library /home/user/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
INFO    | added library /home/user/Android/Sdk/emulator/lib64/vulkan/libvulkan.so
INFO    | Started GRPC server at 127.0.0.1:8554, security: Local
INFO    | Advertising in: /run/user/1000/avd/running/pid_34417.ini
INFO    | boot completed
INFO    | boot time 18182 ms
INFO    | Increasing screen off timeout, logcat buffer size to 2M.
INFO    | Revoking microphone permissions for Google App.
INFO    | Shutting down gRPC endpoint
INFO    | Shutting down gRPC endpoint
[user@spreewald ~]$ emulator -avd Pixel_5_API_31 
INFO    | Android emulator version 31.2.8.0 (build_id 8143646) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
WARNING | cannot add library /home/user/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
INFO    | added library /home/user/Android/Sdk/emulator/lib64/vulkan/libvulkan.so
INFO    | configAndStartRenderer: setting vsync to 60 hz
INFO    | Sending adb public key [QAAAAHdcD7y5wszq/Z6ijjQGMKm/h0Br8lo5+woeTY6a0XOHfHHqoLUI6QO1Gea4pKLWAvZxYtp8BF62jGZ+P2jqsJscKalVgwtdO33zqrPjMoQ+u1uKHumZzSndHTpwAlINzoAFyvwP5bgSy+q4eImD7MEJmOSuNYUnRYjqCneC9O6yvr4QgrkBpD3uikgF2nTNvtelm9pEkUz+WMueJ1D6RbCXEsrrs9Aflb4P8O/fl6zq70YUt4gWczYeDQ1jci28y5e3yR73RDARjLD9DiEGiY3+HdL6NPnvBRx/jdxN0bY6FhLHAwGJFxAd+2DuyJ9bh22RM1tl0CYmJcrz7Wx3mQtjcwyVAgTXxmaB8oe2A9UH9vfDSjgS15D9n7ICy20jePzMTDX1NAv5IY+gAlShosbf8p0ZTGLyB87/nGal2z20YRGlNfaBMXdxmI5O64HLz8CwZ4OUCXLdI5orwCv1DgE697sQjHbtYOcxOFjAvXNoICTrxtP6RLdm3Tp3V3CmtXgiE10ZgtbvTBS7LBAThxV01yWQmtc9ZKUzegduBnwJVMSp/Qee3AanQEL0yWy7+CoVUeznNfsOIeDass+729KXM29pw/x203BXihebZ/j4orXwKPH0MICLL7KGVJnkVT1erlYOheE3INtclkjmat+hzQQyYEHryYM2o1XF35Ad0RLWRQEAAQA= user@unknown]
INFO    | Rootcanal has  been activated.
INFO    | Started GRPC server at 127.0.0.1:8554, security: Local
INFO    | Advertising in: /run/user/1000/avd/running/pid_34903.ini
INFO    | boot completed
INFO    | boot time 22001 ms
INFO    | Increasing screen off timeout, logcat buffer size to 2M.
INFO    | Revoking microphone permissions for Google App.
error: kvm run failed Bad address
RAX=00007a2f6b801000 RBX=00007a2f6b8baa00 RCX=0000000000000000 RDX=00000000000b9a00
RSI=0000000000801000 RDI=00007a2f6b801000 RBP=00000000000b9a00 RSP=00007a2f7b21ce50
R8 =00007a2f6b802000 R9 =00007a2f7b21cee0 R10=00002ea0002f8000 R11=0000000000000213
R12=00000000000000b0 R13=0000000000000000 R14=00007a2f6b801000 R15=00000000000010e0
RIP=00007a3281b28d24 RFL=00000206 [-----P-] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =0000 0000000000000000 00000000 00000000
CS =0033 0000000000000000 ffffffff 00a0fb00 DPL=3 CS64 [-RA]
SS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
DS =0000 0000000000000000 00000000 00000000
FS =0000 00007a2f7b221000 00000000 00000000
GS =0000 00007a3151e3d5e0 00000000 00000000
LDT=0000 0000000000000000 00000000 00000000
TR =0040 fffffe00000a2000 00004087 00008b00 DPL=0 TSS64-busy
GDT=     fffffe00000a0000 0000007f
IDT=     fffffe0000000000 00000fff
CR0=80050033 CR2=00007a2f6c002000 CR3=000000002c780000 CR4=000406a0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=41 0f 6f 4c 30 10 f3 41 0f 6f 54 30 20 f3 41 0f 6f 5c 30 30 <66> 41 0f 7f 00 41 0f 29 48 10 41 0f 29 50 20 41 0f 29 58 30 4d 8d 40 40 4c 39 c3 77 bf 48
WARNING | Not saving state: current state does not support snapshotting
INFO    | Deleting snapshot default_boot
INFO    | Shutting down gRPC endpoint
INFO    | Shutting down gRPC endpoint
INFO    | Closing down rootcanal.

Studio Build: Version of Gradle Plugin: Version of Gradle: Version of Java: OS: Emulator Version: 31.2.8-8143646 Android Version: 2.0 (S) - API 31 AVD Image:Pixel 5 Android 12.0 Google APIs | x86_64 Android SDK PlatformTools: 33.0.0 Host CPU: AMD Ryzen 7 PRO 5850U hw,device.name: pixel_5

Screenshot_20220321_142529.png

8.2 KB

View

Download

Comments

hu...@google.com <hu...@google.com> Mar 22, 2022 08:13PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> Mar 23, 2022 06:45PM

Reassigned to ya...@google.com.

ya...@google.com <ya...@google.com> #2Mar 23, 2022 09:15PM

Thank you for this feedback. The team may reach out for more information on triaging or reproducing this issue.

jb...@gtempaccount.com <jb...@gtempaccount.com> #3Mar 24, 2022 03:49PM

I have tried the example project you've provided, it does not reproduce.

Could you please try running with -Pandroid.useDexArchive=false? This disables the new dexing pipeline, and fallbacks to the old one.

ya...@google.com <ya...@google.com> #4Mar 24, 2022 05:59PM

@Mario Did you get a chance to try the build with -Pandroid.useDexArchive=false flag?

jb...@gtempaccount.com <jb...@gtempaccount.com> #5Mar 29, 2022 07:53AM

I'm the college of @Mario and I make it work without issues and without using -Pandroid.useDexArchive=false by using alpha6 and removing retrolambda

ya...@google.com <ya...@google.com> #6Mar 29, 2022 07:02PM

Sorry my comment from Apr 21, 2017 12:41PM was wrong.
With -Pandroid.useDexArchive=false it looks like this

:app:transformClassesWithDesugarForNonpayItalyCompatDebugAndroidTest
:app:transformClassesWithPreDexForNonpayItalyCompatDebugAndroidTest
Dex: warning: Ignoring InnerClasses attribute for an anonymous inner class
(org.ccil.cowan.tagsoup.Parser$1) that doesn't come with an
associated EnclosingMethod attribute. This class was probably produced by a
compiler that did not target the modern .class file format. The recommended
solution is to recompile the class from source, using an up-to-date compiler
and without specifying any "-target" type options. The consequence of ignoring
this warning is that reflective operations on this class will incorrectly
indicate that it is *not* an inner class.

:app:transformDexWithDexForNonpayItalyCompatDebugAndroidTest FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexWithDexForNonpayItalyCompatDebugAndroidTest'.
> com.android.build.api.transform.TransformException: com.android.ide.common.process.ProcessException: java.util.concurrent.ExecutionException: com.android.dex.DexIndexOverflowException: method ID not in [0, 0xffff]: 65536

ya...@google.com <ya...@google.com> #7Mar 29, 2022 07:02PM

We updated our example repo

https://github.com/originx/Gradle_troubles_android_enteprise where you can see the issue.
Just run

./gradlew spoonGermanyDebugAndroidTest
or
./gradlew spoonGermanyDebugAndroidTest -Pandroid.useDexArchive=false

and you will see the issue

jb...@gtempaccount.com <jb...@gtempaccount.com> #8Mar 30, 2022 01:50PM

Your tests do not fit into a single dex file. I've tried plugin 2.3.0 (I've also had to enable retrolambda for app, core, and pay modules), and the number of references that are generated is higher than 64k.
Please note that if you are using plugin's internal or Retrolamba support for Java 8 language features, for each lambda expression you will generate 3 additional references, so it might affect your reference count quite significantly.

ya...@google.com <ya...@google.com> #9Mar 30, 2022 04:34PM

Hello and thank you for the reply. What is the expected fix for this the ticket status was moved to "verified (fixed)" it is rather confusing for me. Do you suggest we have too many tests and that's it?
Could you please clarify?
Thank you for your time

jb...@gtempaccount.com <jb...@gtempaccount.com> #10Mar 30, 2022 06:37PM

Your test sources and test-only dependencies are generating too many references. Java 8 language features are not related to this, as even when I remove compileOptions from all modules, the test dependencies cannot fit into a single dex file.

I suggest you take a look at Proguard rules that you can specify when running the tests -

https://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.ProductFlavor.html#com.android.build.gradle.internal.dsl.ProductFlavor:testProguardFile(java.lang.Object). I've also updated the bug status, not to be confusing.

ya...@google.com <ya...@google.com> #11Mar 30, 2022 09:32PM

Hello,

Thank you for the link and clarification.
Pardon my many questions I just want to understand the problem better.

We use proguard for the app and define proguard rules which classes to keep for the test runner that we need early on in the start of the test run.
Why did it work with older build tools?
Also why doesnt multidex work for the test app or proguard rules from the debug builds?

Thank you for the quick response

ni...@gmail.com <ni...@gmail.com> #12Nov 3, 2022 05:44PM

No worries Mario, I would also like to understand where the issue is coming from :)

The fact that it worked with 2.3.0 and not with 2.4.0-alpha4 is worrying. Because I am unable to reproduce with the test project you've provided, can you please compare the contents of build/intermediates/transforms/preDex/androidTest/ when building tests:
- from clean, with 2.3.0
- from clean, with 2.4.0-alpha4, with -Pandroid.useDexArchive=false
The content of these 2 directories should be the same. Please report any differences.

The support in the test runner is missing to be able to run test apk with multiple DEX files. I don't have much more info on it, sorry.

sa...@exalt.ps <sa...@exalt.ps> #13Nov 22, 2022 10:49AM

Hello,

sorry I am a bit restricted in the work environment so I cannot build the demo project from this location but I executed a diff on a real project where the issue happens for dex folders (predex is not available in 2.3.0) its disabled for our project.

this is for 2.3.0 and 2.4.0-alpha4 in location build/intermediates/transforms/dex/androidTest/nonPayMexicoBleeding for following command:
./gradlew clean connectedNonpayMexicoBleedingDebugAndroidTest
I used flag -Pandroid.useDexArchive=false for 2.4.0 only.

diff -rq nonpayMexicoBleeding\ 2.3.0/ nonpayMexicoBleeding\ 2.4.0-alpha4/
Result:
Only in nonpayMexicoBleeding 2.3.0/debug/folders/1000: 1
Only in nonpayMexicoBleeding 2.3.0/debug/folders/1000: 10
Only in nonpayMexicoBleeding 2.4.0-alpha4/debug/folders/1000: 1f

Does this help?

ya...@google.com <ya...@google.com> #14Nov 22, 2022 06:31PM

Marked as fixed.

I updated the demo project so you have reproducable example:

https://github.com/originx/Gradle_troubles_android_enteprise

./gradlew clean connectedNonpayMexicoBleedingDebugAndroidTest

Gradle 3.4.0-alpha7 breaks
Commit: ca9e7f7134e5418f9e27e3164efe25521a324a46

Gradle 3.1.2 works
Commit: cfa48cf0b25427d48b328ef6cf80d51fc4e5933b

Cheers

rv...@gmail.com <rv...@gmail.com> #15Nov 28, 2022 07:14PM

Comment has been deleted.

Message last modified on Nov 28, 2022 07:14PM

le...@gmail.com <le...@gmail.com> #16Dec 20, 2022 10:47AM

It works with 2.3.1 because we do not merge the individual dex files, so every test dependency gets dexed individually, and packaged in the test APK. In 2.4.0-alpha7, we are merging all test dependencies to a DEX file, and in this case, they do not fit.

ya...@google.com <ya...@google.com> #17Dec 20, 2022 06:05PM

Status: Assigned (reopened)

so we would need to turn on multidex on the test APK to make this work ?

[Deleted User] <[Deleted User]> #18Dec 27, 2022 04:19PM

I think we can do the following:
- If the tested app is mono-dex, test will be mono dex for < 21, and multidex for 21+.
- If the tested app is native multidex, test is as well.
- And if the tested app is legacy multidex, test is mono dex (because currently the test runner does not support pre 21 test multidex apks).
WDYT?

su...@innomatic.ca <su...@innomatic.ca> #19Dec 28, 2022 06:22PM

Hello,

Sounds like a solution that would make it work on gradle 3.4.0>= ?

What are the side effects from the architecture point of view, performance etc, depending on the effort there would it pay off to bring full multidex support to test runner and test apk both?

I always find it confusing what is the difference between:
-multidex test apk
-multidex test runner

I thought that multidex apk is already supported by MultidexInstrumentationTestRunner

https://developer.android.com/reference/com/android/test/runner/MultiDexTestRunner.html

so that should work, or are you suggesting to introduce the multidex support to the test runner also (what is less effort and more benefit from your side? )

Best regards & thanks for your time

Message last modified on Dec 28, 2022 06:32PM

da...@gmail.com <da...@gmail.com> #20Dec 30, 2022 05:58PM

I am not sure when the fix would land (hopefully in the next 1-2 canary releases).
For api levels 21+, ART supports multidex for both the test apk and tested apk, so nothing needs to be done there, and there is no performance penalty. However, multidex for < 21 requires patching the class loader, which is done by the test runner for the tested APK. The test runner is unable to patch the class loader for the test apk though, and we this change is not going to change that. So if you are testing your application with min sdk below 21, you will still have to make sure that the test apk contains a single DEX file.

iv...@gmail.com <iv...@gmail.com> #21Jan 9, 2023 09:50PM

Hello,

thank you for the explanation. But I still dont understand why did it work before for api <21, what broke it?

Will that be fixed?

Thank you for your time.

cc...@logitech.com <cc...@logitech.com> #22Jan 17, 2023 03:53PM

You might have been able to build a multidex test apk for api < 21, but I am pretty sure you were not able to run all tests on a device < 21 unless you've written your own test runner that patches the class loader. I'd like to avoid this runtime failure scenario. We should break the build until the support for legacy multidex test apk is added.

ya...@google.com <ya...@google.com> #23Jan 17, 2023 10:05PM

Reassigned to ca...@google.com.

Hello,

If this is a decision from the Android team, could you at least give us instructions how to do this patching on our own. I am amazed that we did not see so much breaking problems up until now, but you are telling us that technically we had a bug/s that is now exposed with the change you guys did now.
Is there a way to add this manual patching by ourselves then, and how to do it?

Thx for the support.

ca...@google.com <ca...@google.com> #24Jan 20, 2023 12:10AM

Reassigned to ya...@google.com.

There is a work in progress to add the support for the legacy multidex test apks, but I am not sure when it might land -

https://android-review.googlesource.com/#/c/276561/.

Mac M1.mov

107 MB

Download

ya...@google.com <ya...@google.com> #25Jan 20, 2023 12:17AM

Reassigned to aw...@google.com.

I understand I will take a look at the commits and try to understand what was done there.
Is there a way to connect this bug to that commit and somehow get an ETA, we rely heavily on our instrumentation for a safety net and this is a show stopper for us so I need to relay and prioritize this information accordingly in the company.

To be honest the biggest worry for me here is that some of the classes you have there are package protected e.g. MultidexExtractor (from the first glance) so I would have to find a way to find proper list of dex files created from test apk, instrumentation and the app and sum them together in the test runner, not sure can I duplicate this behaviour but I will take a look in it in more detail starting next work week.

ya...@google.com <ya...@google.com> #26Jan 20, 2023 12:21AM

Hello, the merge strategy for commits you sent is: "Strategy Merge if Necessary"
Could we link this bug to the commits and merge them in 2.4.0?

Thanks

aw...@google.com <aw...@google.com> #27Jan 20, 2023 02:41PM

Reassigned to ca...@google.com.

ag/I6425e061a2d5e97e36c56fc01c009475af62c086 allows native multidex test apks. Legacy multidex tested app still requires mono-dex test apk. It should be released in the next canary release of the plugin.

@Mario The change is part of the multidex support library, and that is released as part of the SDK (not plugin nor Android Studio). Once the change is in, I will work on adding the support in the plugin. Unfortunately, I cannot provide any ETA. The owner of that change is aware of this bug (it is referenced from an internal bug report that is assigned to him).

ca...@google.com <ca...@google.com> #28Jan 25, 2023 12:46AM

Reassigned to aw...@google.com.

So the TL;DR is:

1. using native multidex, the fix will be available in the next gradle plugin releases (after 2.4.0-alpha7)
2. using legacy (i.e. support) multidex, we'll have to wait until a new release of com.android.support:multidex:1.0.x library

Do I have that right?

wb...@gmail.com <wb...@gmail.com> #29Jan 26, 2023 03:43PM

Yes, that is correct.

ya...@google.com <ya...@google.com> #30Jan 26, 2023 06:11PM

"We should break the build until the support for legacy multidex test apk is added."

This causes quite a bit of pain for my team. We currently have a test apk with more than 65k referenced methods (we're already running proguard on the test apk), and we're depending on it building properly. Our minSdkVersion is 18, but we only run our instrumentation tests on API 21+, so the old behavior allowed us to continue running our tests.

With the new behavior in AGP 3.0, our test apk fails to even build. It seems like my only options are:
1) Reduce the number of referenced methods
2) Create a new variant or flavor with minSdk 21+ and use that for running tests
3) Use minSdk 21 for all debug builds

The first option isn't really feasible, and the second is massively painful because it requires us to retrain 50+ devs on which gradle commands to use to run tests (since the commands change when adding a variant or flavor). The third option also isn't ideal because then we lose lint validation for our real minSdkVersion and lose the ability to easily run debug builds on older android versions manually.

Is there any way to keep the behavior from AGP 2.3.x for building test apks until a proper solution for legacy multidex is available?

wb...@gmail.com <wb...@gmail.com> #31Feb 7, 2023 09:21AM

@dr... for your specific situation, why not just stay on 2.3 until 2.4 (or 3.0) is out of alpha? Having 50 devs on alpha anything seems really iffy.

wb...@gmail.com <wb...@gmail.com> #32Feb 9, 2023 10:41AM

Yeah, definitely. We're not planning to upgrade until 3.0 is stable, but I'm worried that it will get to the stable channel without this being fixed. If legacy multidex support for test apks is ready before 3.0 is stable, then I don't have a problem :)

le...@gmail.com <le...@gmail.com> #33Feb 21, 2023 08:20AM

Hello,
since the multidex 1.0.2 is live I would expect that multidex works fine on api <21 for test apks, but this is not the case.
Did I misunderstand something when you said this will be backported to legacy multidex so test apk can contain multiple dex files also or?

classpath 'com.android.tools.build:gradle:3.0.0-alpha7'
multidex : '1.0.2',
Android Studio 3.0 Canary 7
Build #AI-171.4182969, built on July 14, 2017
JRE: 1.8.0_152-release-884-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.4

Message last modified on Feb 21, 2023 08:22AM

aw...@google.com <aw...@google.com> #34Feb 27, 2023 05:52PM

The support for legacy multidex test apks has been merged in AOSP, but a new version of com.android.support:multidex has not been published yet. We need this artifacts published in order to add support for legacy multidex test apks in the Android plugin for Gradle.

aw...@google.com <aw...@google.com> #35Mar 9, 2023 06:13PM

Marked as fixed.

Hello,
Thank you for the answer but I don't understand what is inside multidex 1.0.2 then.

in support lib Revision 25.4.0 it is stated:
Concurrent with this support library release, we are also releasing multidex version 1.0.2. This version includes the following important changes:
Allows multidexing of instrumentation APK.
Deprecates MultiDexTestRunner (AndroidJUnitRunner should be used instead).

We use multidex 1.0.2. Does this mean this fix will come out in 1.0.3, do you have any eta window on this topic?

Cheers

le...@gmail.com <le...@gmail.com> #36Mar 17, 2023 11:07AM

Indeed, 1.0.2 contains all the necessary support, but the support in the plugin is missing. I will try to get the plugin changes published in the next few preview releases, but I cannot give any hard guarantees when it will happen.

oe...@gmail.com <oe...@gmail.com> #37Mar 17, 2023 07:11PM

Thank you for the clarification. Could you please update the documentation that the new support/ multidex lib is not integrated in tooling yet. Also in gradle build files lint recommends removing the "dev" flavor since it is not needed anymore but then it would break tests, instant run etc. also an important thing to note.
Looking forward to the integration let us know when you manage to merge it.
Have a nice weekend!

graphics_setting_android_emulator.PNG

24 KB

View

Download

jo...@spork.tech <jo...@spork.tech> #38Mar 31, 2023 02:15PM

I am reopening this, as we have too many reports. It is blocked on internal issue

b/62286076

ro...@veeva.com <ro...@veeva.com> #39Apr 11, 2023 11:28AM

hello, what is the current progress of this issue?

thank you

aw...@google.com <aw...@google.com> #40Apr 11, 2023 02:02PM

@39 The support in the plugin is ready, however we need a new version of build tools published. Hopefully that will happen soon.

ja...@gmail.com <ja...@gmail.com> #41Apr 11, 2023 02:03PM

this is amazing news, could you please update the status of this ticket when this happens?

does this mean this will come out with beta4?

ro...@veeva.com <ro...@veeva.com> #42Apr 11, 2023 02:05PM

Build tools are published independently of the plugin and Android Studio, but I hope that will happen in the next week or two. I'll update the bug once it happens.

aw...@google.com <aw...@google.com> #43Apr 11, 2023 02:08PM

Status: Assigned (reopened)

@42 1.0.2 does provide support for multidex android test APKs.

Simply create a "CustomerTestRunner" and override "onCreate" to call "MultiDex.installInstrumentation(context, targetContext)". See this example:

https://github.com/jaredsburrows/android-gif-example/blob/master/src/androidTest/kotlin/test/CustomTestRunner.kt#L12.

ro...@veeva.com <ro...@veeva.com> #44Apr 11, 2023 02:13PM

It seems that multidex 1.0.2 works with multidex test apks for AGP 2.3.0, not 3.0.0+.

hs...@google.com <hs...@google.com> #45Jun 28, 2023 06:35PM

#44 Make sure you use ATSL runner 1.0.1 or later.

pc...@gmail.com <pc...@gmail.com> #46Jul 1, 2023 11:15AM

I am:

https://github.com/jaredsburrows/android-gif-example/blob/master/gradle/versions.gradle.kts#L75.

Message last modified on Jul 1, 2023 12:30PM

t9...@gmail.com <t9...@gmail.com> #47Jul 6, 2023 08:10AM

We discovered this problem too. It's quite annoying for us and we will have to reverse switching to GAP 3 if there is no fix in the next 2 days...

Can anyone give us an update and an ETA for this ?
We use build tools 26.0.1, gap 3 beta 5, ASTL runner 1.0.1.

le...@gmail.com <le...@gmail.com> #48Jul 8, 2023 02:00PM

As a workaround, how can we run proguard on the instrumentation apk, when it is not enabled in our debug variant for the main app ?

hs...@google.com <hs...@google.com> #49Jul 10, 2023 11:21PM

You do not want to proguard a debug apk. It would take forever to write and
run new tests.

Jared Burrows

*jaredsburrows@gmail.com <jaredsburrows@gmail.com>*
LinkedIn:

https://www.linkedin.com/in/jaredsburrows

On Thu, Sep 14, 2017 at 12:14 PM, <buganizer-system@google.com> wrote:

- Show quoted text -

hs...@google.com <hs...@google.com> #50Jul 11, 2023 05:14PM

Until this issue is fixed, many apps will have no choice but to proguard their test apk :)

ed...@gmail.com <ed...@gmail.com> #51Aug 31, 2023 09:04AM

I agree, this workaround is not a good solution.

ya...@google.com <ya...@google.com> #52Aug 31, 2023 05:32PM

On our side, we fixed the issue by cutting down on our dependencies in the instrumentation apk. Though the dex count is still in the red zone and we will be happy to see the issue fix, but there is no more emergency on our side.

bo...@google.com <bo...@google.com> #53Sep 12, 2023 02:19AM

Fixed, bug tracking the release :

https://buganizer.corp.google.com/issues/65838025

hs...@google.com <hs...@google.com> #54Sep 13, 2023 04:41PM

Reassigned to ya...@google.com.

I see it is tracked in Moma. Is this set for marked release for 3.0.0-beta7? or release?

ya...@google.com <ya...@google.com> Sep 13, 2023 06:24PM

Reassigned to aw...@google.com.

hs...@google.com <hs...@google.com> #55Sep 14, 2023 08:13PM

was the fix included in the latest release of build tools 26.1? I think the link to track the release is not public.

bo...@google.com <bo...@google.com> #56Sep 14, 2023 10:57PM

It still doesn't work for me on 3.0.0-beta7 and Build tools 26.0.2 - I still get the error.

hs...@google.com <hs...@google.com> #57Sep 14, 2023 11:18PM

Status says fixed but could we get instructions on how to make it work? Is this already included in Build tools 26.0.2 and AGP 3.0.0-beta7?

hs...@google.com <hs...@google.com> #58Sep 14, 2023 11:21PM

Same problem here... I don't see this issue as fixed

hs...@google.com <hs...@google.com> #59Sep 14, 2023 11:35PM

The issue has not been fixed in beta7, as build tools 26.0.2 are missing some of the pieces to have this working. Re-opening.

bo...@google.com <bo...@google.com> #60Sep 14, 2023 11:38PM

Thank you.

rk...@google.com <rk...@google.com> #61Sep 14, 2023 11:39PM

Is there an ETA? Looks like build tools 27.0.0 shipped without this fix.

bo...@google.com <bo...@google.com> #62Sep 14, 2023 11:41PM

Any ETA on this? Or which components we should watch for updates? Is the the build tools 2x.0.y? Is it a new multidex support lib 1.0.3? 3.1 plugin?

hs...@google.com <hs...@google.com> #63Sep 14, 2023 11:42PM

Sorry, we don't commit to timelines on public bugs.

All the changes needed are submitted to the four components (build tools, MultidexTestRunner, AndroidJunitRunner and android gradle plugin) and we'll update this bug as soon as it is released, so it will be in Android Gradle Plugin 3.1.

Note that both the deprecated MultiDexTestRunner and the replacement AndroidJUnitRunner will support legacy multidex test APKs

hs...@google.com <hs...@google.com> #64Sep 14, 2023 11:45PM

Could you consider releasing the fix under 3.0.x (if that's even possible)?
Doing it in 3.1 will require everyone who wants to have multidex for test APK working to start using unstable version of AS and AGP.

rk...@google.com <rk...@google.com> #65Sep 14, 2023 11:46PM

Please update documentation to reflect that legacy multidex IS supported, except broken by this bug (known issue) in AGP 3.0.

https://developer.android.com/studio/build/multidex.html#testing

> `Using multidex to create a test APK is not currently supported.`

hs...@google.com <hs...@google.com> #66Sep 14, 2023 11:49PM

This is fixed starting with 3.1.0-alpha04. Please try it out, and let us know if you are facing any issues. Thanks!

hs...@google.com <hs...@google.com> #67Sep 14, 2023 11:53PM

Is it not "MultiDex.installInstrumentation(getContext(), getTargetContext());" in the AndroidJUnitRunner?

rk...@google.com <rk...@google.com> #68Sep 15, 2023 04:30AM

3.1.0-alpha04 worked for me. Thanks for the fix.

ya...@google.com <ya...@google.com> #69Sep 15, 2023 05:00PM

I just trying with 3.1.0-alpha06 and the problem seams to still be there =/

bo...@google.com <bo...@google.com> #70Sep 15, 2023 06:20PM

This isn't working for me either with 3.1.0-alpha06. Can you clarify what was fixed, and what combination of Gradle, Android Gradle Plugin, Multidex library and Android Build Tools we should test against?

hs...@google.com <hs...@google.com> #71Sep 15, 2023 07:10PM

Folks, any news in this issue? Could you explain how to make this work? Simply using AGP 3.1.0-alpha04 doesn't solve the problem

hs...@google.com <hs...@google.com> #72Sep 15, 2023 07:16PM

Never mind. It does solve the problem

bo...@google.com <bo...@google.com> #73Sep 15, 2023 10:38PM

Re #70:
You need to use Android plugin for Gradle 3.1.0-alpha04+, any compatible version of Gradle (e.g. 4.4) and BuildTools (e.g. 27.0.3). Multidex library 1.0.2 will be added by the plugin as a dependency automatically. With this, your build will be successful.

To run tests successfully, the test runner needs to support legacy test APK. AndroidJUnitRunner supports that, so you can use that.

hs...@google.com <hs...@google.com> #74Sep 18, 2023 04:39PM

Looks much better but I still get an issue with multiDexKeepProguard file, it somehow feels it is not respected which classes should be added to the main dex file.
For example following your suggestion of tl;dr version the test crashes because some files are not found in the main dex file during the app start:

01-09 10:31:06.965 4861-4861/? W/dalvikvm: Class resolved by unexpected DEX: Ltimber/log/Timber$Tree;(0xa75def58):0x99f02000 ref [Lcom/google/devtools/build/android/desugar/runtime/ThrowableExtension;] Lcom/google/devtools/build/android/desugar/runtime/ThrowableExtension;(0xa75def58):0x99caf000
01-09 10:31:06.965 4861-4861/? W/dalvikvm: (Ltimber/log/Timber$Tree; had used a different Lcom/google/devtools/build/android/desugar/runtime/ThrowableExtension; during pre-verification)
01-09 10:31:06.965 4861-4861/? D/AndroidRuntime: Shutting down VM
01-09 10:31:06.965 4861-4861/? W/dalvikvm: threadid=1: thread exiting with uncaught exception (group=0xa66de228)
01-09 10:31:06.975 4861-4861/? E/InstrumentationResultPrinter: Failed to mark test No Tests as finished after process crash
01-09 10:31:06.975 4861-4861/? E/MonitoringInstr: Exception encountered by: Thread[main,5,main]. Dumping thread state to outputs and pining for the fjords.
java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation
at timber.log.Timber$Tree.getStackTraceString(Timber.java:569)
at timber.log.Timber$Tree.prepareLog(Timber.java:544)
at timber.log.Timber$Tree.i(Timber.java:452)
at timber.log.Timber$1.i(Timber.java:288)
at timber.log.Timber.i(Timber.java:63)

Do you have any idea where does this pops out from?

hs...@google.com <hs...@google.com> #75Sep 19, 2023 08:22PM

Re #74:
This seems to be Java 8 specific bug, and I've filled

https://issuetracker.google.com/71737186 to track this. Can we please continue discussion there?

hs...@google.com <hs...@google.com> #76Sep 19, 2023 08:23PM

We would love to use this fix, but we need a stable version of the gradle android plugin. When will Gradle Android Plugin 3.1.0 be released ?

ro...@veeva.com <ro...@veeva.com> #77Sep 20, 2023 07:33AM

"Please " help me i want update oreo 8.0 without computer

hs...@google.com <hs...@google.com> #78Sep 20, 2023 06:02PM

The release note for 3.1.0 doesn't mention this issue, is it fixed ?

hs...@google.com <hs...@google.com> #79Sep 20, 2023 06:04PM

We are trying it and it looks like it's not working (though it used to be working in alpha04)

bo...@google.com <bo...@google.com> #80Sep 20, 2023 07:35PM

There is a bug of a new kind in 3.1 + related to instrumented APKs & multidex

Until recently we had a big module, with all our code + all our instrurmentation tests code. Then we could check and the plugin (3.1.alpha and 3.1) work well to enable multidex in tests apks.
But we recently dissociated this big module: one contains the production code, the other one contains the instrumentation code. And then, the new plugin breaks: we can still a multidex production app, but the instrumentation test apk is not generated. We hit the 65K limit and the build reports this as an issue. Also, the android test don't have a task: transformClassesWithMultidexlistFor<variant>AndroidTest

What can go wrong ?

bo...@google.com <bo...@google.com> #81Sep 20, 2023 07:36PM

To be more precise: we have one module named module_apk that contains:
* a few classes in production code
* quite a lot of classes of instrumentation tests

The module_apk wires together all other modules that are all library modules.

When adding multidexEnabled to module_apk, the production apk is multidexed, but not the test apk. There is no transform / task for the AndroidTest variant related to multidex.
When adding multidexEnabled to all default configuration of all modules, all of them have both instrumentation and production multidex tasks & transformations, all except module_apk...

We have no idea what is going wrong.

aw...@google.com <aw...@google.com> #82Sep 20, 2023 07:43PM

Re #81:
I've filled

https://issuetracker.google.com/77183226, let's please continue discussion there. Thanks.

bo...@google.com <bo...@google.com> #83Sep 21, 2023 01:35PM

What went wrong:
Execution failed for task ':app:transformClassesWithMultidexlistForLive'.
> com.android.build.api.transform.TransformException: Error while generating the main dex list.

em...@gmail.com <em...@gmail.com> #84Sep 21, 2023 06:34PM

Re #83: Please file a new issue, as that is error indicates there is a main dex list task error for the application, not for the test.

bo...@google.com <bo...@google.com> #85Sep 27, 2023 03:46PM

Echoing #78. Our instrumented tests using multidex worked using the 3.0.0 version of the Android Plugin for gradle. Updated to 3.1.1 and it would just say empty test suite. I found this bug then reverted back to 3.1.0-alpha04 and the tests work again. Should this be working in 3.1.1?

bo...@google.com <bo...@google.com> #86Sep 28, 2023 06:34PM

We (whoever has a repro) should probably file a new issue against 3.1.1 referencing this issue. This has been "marked as Fixed" 3 times... so it's possible the current problems are far from the original.

hs...@google.com <hs...@google.com> #87Sep 28, 2023 11:22PM

Re #85, #86:

Yes, please file a new bug, and paste the link here. Issue in #78 was due to a custom plugin which would disable multidex. Thanks!

ro...@veeva.com <ro...@veeva.com> #88Sep 29, 2023 08:02AM

Cool. Created

https://issuetracker.google.com/u/1/issues/78108767 for this

bo...@google.com <bo...@google.com> #89Oct 2, 2023 03:50PM

I rebuilt the kvm and kvm-intel.ko on my linux 6.3.11,
with BUG_ON the EFAULT

static int __kvm_write_guest_page(struct kvm *kvm,
struct kvm_memory_slot *memslot, gfn_t gfn,
const void *data, int offset, int len)
{
int r;
unsigned long addr;

addr = gfn_to_hva_memslot(memslot, gfn);
if (kvm_is_error_hva(addr)) {
BUG_ON(1); // here is the fault place
return -EFAULT;
}
r = __copy_to_user((void __user *)addr + offset, data, len);
if (r) {
BUG_ON(1);
return -EFAULT;
}
mark_page_dirty_in_slot(kvm, memslot, gfn);
return 0;
}

[604038.258580] kvm_intel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and

https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
[604223.571707] ------------[ cut here ]------------
[604223.571707] ------------[ cut here ]------------
[604223.571711] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:3125!
[604223.571713] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:3125!
[604223.571724] invalid opcode: 0000 [#1] PREEMPT SMP PTI
[604223.571731] CPU: 10 PID: 1928475 Comm: MainLoopThread Tainted: P W OE 6.3.11-1rodete2-amd64 #1 Debian 6.3.11-1rodete2
[604223.571738] Hardware name: LENOVO 30BFS44D00/1036, BIOS S03KT40A 08/12/2020
[604223.571742] RIP: 0010:__kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.571922] Code: cc cc cc 4c 89 e0 48 2b 86 b0 00 00 00 48 3b 86 b8 00 00 00 48 19 c9 48 21 c8 48 c1 e0 0c 48 03 86 f8 00 00 00 49 89 c5 eb 8c <0f> 0b 0f 0b 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90
[604223.571928] RSP: 0018:ffffbfe943313b98 EFLAGS: 00010246
[604223.571934] RAX: 0000000000000000 RBX: 0000000000000002 RCX: ffff9decd2a4bf80
[604223.571938] RDX: 000000000080005f RSI: 0000000000000000 RDI: ffffbfe9425bd000
[604223.571942] RBP: 0000000000000002 R08: 0000000000000000 R09: 0000000000000002
[604223.571946] R10: 00000000ffffffff R11: ffff9decc8ca8290 R12: 000000000080005f
[604223.571950] R13: ffff9decd2a4bf80 R14: ffff9decc8ca8000 R15: 0000000000000000
[604223.571954] FS: 00007f548fc836c0(0000) GS:ffff9dfc00080000(0000) knlGS:0000000000000000
[604223.571959] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[604223.571963] CR2: 0000000013365000 CR3: 0000000b741fe002 CR4: 00000000003726e0
[604223.571967] Call Trace:
[604223.571972] <TASK>
[604223.571979] ? die+0x36/0x90
[604223.571988] ? do_trap+0xda/0x100
[604223.571995] ? __kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.572197] ? do_error_trap+0x6a/0x90
[604223.572204] ? __kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.572415] ? exc_invalid_op+0x50/0x70
[604223.572423] ? __kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.572633] ? asm_exc_invalid_op+0x1a/0x20
[604223.572650] ? __kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.572864] kvm_vcpu_write_guest+0x59/0xb0 [kvm]
[604223.573080] write_emulate+0x23/0x50 [kvm]
[604223.573312] emulator_read_write_onepage+0xea/0x330 [kvm]
[604223.573547] ? linearize.isra.0+0x1eb/0x290 [kvm]
[604223.573795] emulator_read_write+0xbf/0x160 [kvm]
[604223.574030] x86_emulate_insn+0x596/0xe50 [kvm]
[604223.574278] x86_emulate_instruction+0x31a/0x7d0 [kvm]
[604223.574519] vmx_handle_exit+0x86b/0x9e0 [kvm_intel]
[604223.574567] kvm_arch_vcpu_ioctl_run+0x6d5/0x1750 [kvm]
[604223.574817] kvm_vcpu_ioctl+0x199/0x6d0 [kvm]
[604223.575028] ? do_syscall_64+0x6b/0xc0
[604223.575039] ? __audit_filter_op+0xaf/0x110
[604223.575051] __x64_sys_ioctl+0x91/0xd0
[604223.575060] do_syscall_64+0x5c/0xc0
[604223.575069] ? syscall_exit_to_user_mode+0x1b/0x40
[604223.575079] ? do_syscall_64+0x6b/0xc0
[604223.575086] ? do_syscall_64+0x6b/0xc0
[604223.575095] entry_SYSCALL_64_after_hwframe+0x72/0xdc
[604223.575105] RIP: 0033:0x7f54c791b27b
[604223.575122] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[604223.575128] RSP: 002b:00007f548fc82330 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[604223.575136] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f54c791b27b
[604223.575141] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000069
[604223.575146] RBP: 000055a4bac83cf0 R08: 000055a4b92aae1e R09: 00007f548fc81da8
[604223.575151] R10: 000055a4c35a4000 R11: 0000000000000246 R12: 00007f548fc83300
[604223.575155] R13: 00007f548f47c000 R14: 000055a4b93b98c0 R15: 000055a4bac83cf0
[604223.575167] </TASK>
[604223.575170] Modules linked in: kvm_intel(OE) kvm(OE) ufs(E) qnx4(E) hfsplus(E) hfs(E) cdrom(E) minix(E) msdos(E) jfs(E) xfs(E) cpuid(E) nvidia_uvm(POE) tls(E) snd_seq_dummy(E) snd_hrtimer(E) snd_seq(E) snd_seq_device(E) tcp_diag(E) inet_diag(E) nft_chain_nat(E) iptable_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) iptable_filter(E) nf_tables(E) nfnetlink(E) rfkill(E) cpufreq_conservative(E) cpufreq_ondemand(E) cpufreq_powersave(E) cpufreq_userspace(E) nvidia_drm(POE) drm_kms_helper(E) nvidia_modeset(POE) intel_rapl_msr(E) intel_rapl_common(E) intel_uncore_frequency(E) intel_uncore_frequency_common(E) isst_if_common(E) sunrpc(E) skx_edac(E) nfit(E) libnvdimm(E) video(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) binfmt_misc(E) snd_hda_codec_realtek(E) joydev(E) irqbypass(E) rapl(E) intel_cstate(E) snd_hda_codec_generic(E) ledtrig_audio(E) snd_hda_codec_hdmi(E) snd_hda_intel(E) snd_intel_dspcfg(E) snd_intel_sdw_acpi(E) snd_hda_codec(E) snd_hda_core(E) snd_hwdep(E) snd_pcm(E)
[604223.575303] mei_wdt(E) rtsx_usb_ms(E) snd_timer(E) wdat_wdt(E) nvidia(POE) snd(E) think_lmi(E) intel_uncore(E) firmware_attributes_class(E) intel_wmi_thunderbolt(E) wmi_bmof(E) memstick(E) watchdog(E) soundcore(E) mei_me(E) mei(E) ioatdma(E) dca(E) evdev(E) msr(E) parport_pc(E) ppdev(E) lp(E) parport(E) tcp_bbr(E) drm(E) fuse(E) efi_pstore(E) configfs(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) btrfs(E) blake2b_generic(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) nls_ascii(E) nls_cp437(E) vfat(E) fat(E) dm_crypt(E) dm_mod(E) rtsx_usb_sdmmc(E) mmc_core(E) rtsx_usb(E) hid_generic(E) usbhid(E) hid(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) sha512_ssse3(E) sha512_generic(E) nvme(E) nvme_core(E) t10_pi(E) crc64_rocksoft_generic(E) ahci(E) libahci(E) xhci_pci(E) crc64_rocksoft(E) aesni_intel(E) crc_t10dif(E) libata(E) crct10dif_generic(E) xhci_hcd(E) crypto_simd(E) thinkpad_wmi(OE) crct10dif_pclmul(E) cryptd(E) pcspkr(E) intel_lpss_pci(E) crc64(E)
[604223.575458] i2c_i801(E) intel_lpss(E) crct10dif_common(E) e1000e(E) i2c_smbus(E) usbcore(E) scsi_mod(E) idma64(E) scsi_common(E) usb_common(E) wmi(E) button(E) [last unloaded: kvm(OE)]
[604223.575492] invalid opcode: 0000 [#2] PREEMPT SMP PTI
[604223.575501] CPU: 4 PID: 1928474 Comm: MainLoopThread Tainted: P D W OE 6.3.11-1rodete2-amd64 #1 Debian 6.3.11-1rodete2
[604223.575511] Hardware name: LENOVO 30BFS44D00/1036, BIOS S03KT40A 08/12/2020
[604223.575526] ---[ end trace 0000000000000000 ]---
[604223.575516] RIP: 0010:__kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.575804] Code: cc cc cc 4c 89 e0 48 2b 86 b0 00 00 00 48 3b 86 b8 00 00 00 48 19 c9 48 21 c8 48 c1 e0 0c 48 03 86 f8 00 00 00 49 89 c5 eb 8c <0f> 0b 0f 0b 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90
[604223.575813] RSP: 0018:ffffbfe94325fba8 EFLAGS: 00010246
[604223.575821] RAX: 0000000000000000 RBX: 0000000000000004 RCX: ffff9df98b4e7360
[604223.575827] RDX: 00000000000ff001 RSI: 0000000000000000 RDI: ffffbfe9425bd000
[604223.575834] RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000004
[604223.575840] R10: 00000000ffffffff R11: ffff9decc5b44a90 R12: 00000000000ff001
[604223.575847] R13: ffff9df98b4e7360 R14: ffff9decc5b44800 R15: 0000000000000000
[604223.575854] FS: 00007f549048b6c0(0000) GS:ffff9dfbfff00000(0000) knlGS:0000000000000000
[604223.575862] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[604223.575869] CR2: 0000000012c00000 CR3: 0000000b741fe003 CR4: 00000000003726e0
[604223.575875] Call Trace:
[604223.575881] <TASK>
[604223.575887] ? die+0x36/0x90
[604223.575897] ? do_trap+0xda/0x100
[604223.575905] ? __kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.576207] ? do_error_trap+0x6a/0x90
[604223.576216] ? __kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.576497] ? exc_invalid_op+0x50/0x70
[604223.576506] ? __kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.576787] ? asm_exc_invalid_op+0x1a/0x20
[604223.576805] ? __kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.577089] kvm_vcpu_write_guest+0x59/0xb0 [kvm]
[604223.577375] write_emulate+0x23/0x50 [kvm]
[604223.577678] emulator_read_write_onepage+0xea/0x330 [kvm]
[604223.577985] ? linearize.isra.0+0x1eb/0x290 [kvm]
[604223.578306] emulator_read_write+0xbf/0x160 [kvm]
[604223.578614] x86_emulate_insn+0x596/0xe50 [kvm]
[604223.578938] x86_emulate_instruction+0x31a/0x7d0 [kvm]
[604223.579252] vmx_handle_exit+0x86b/0x9e0 [kvm_intel]
[604223.579313] kvm_arch_vcpu_ioctl_run+0x6d5/0x1750 [kvm]
[604223.579635] kvm_vcpu_ioctl+0x199/0x6d0 [kvm]
[604223.579917] ? __audit_filter_op+0xaf/0x110
[604223.579934] __x64_sys_ioctl+0x91/0xd0
[604223.579945] do_syscall_64+0x5c/0xc0
[604223.579956] ? do_syscall_64+0x6b/0xc0
[604223.579965] ? exit_to_user_mode_prepare+0x40/0x1d0
[604223.579980] entry_SYSCALL_64_after_hwframe+0x72/0xdc
[604223.579991] RIP: 0033:0x7f54c791b27b
[604223.580003] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[604223.580012] RSP: 002b:00007f549048a330 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[604223.580022] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f54c791b27b
[604223.580029] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000068
[604223.580036] RBP: 000055a4bac83cf0 R08: 000055a4b92aae1e R09: 0000000000000000
[604223.580042] R10: 0000000000000000 R11: 0000000000000246 R12: 00007f549048b300
[604223.580048] R13: 00007f548fc84000 R14: 000055a4b93b98c0 R15: 000055a4bac83cf0
[604223.580064] </TASK>
[604223.580068] Modules linked in: kvm_intel(OE) kvm(OE) ufs(E) qnx4(E) hfsplus(E) hfs(E) cdrom(E) minix(E) msdos(E) jfs(E) xfs(E) cpuid(E) nvidia_uvm(POE) tls(E) snd_seq_dummy(E) snd_hrtimer(E) snd_seq(E) snd_seq_device(E) tcp_diag(E) inet_diag(E) nft_chain_nat(E) iptable_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) iptable_filter(E) nf_tables(E) nfnetlink(E) rfkill(E) cpufreq_conservative(E) cpufreq_ondemand(E) cpufreq_powersave(E) cpufreq_userspace(E) nvidia_drm(POE) drm_kms_helper(E) nvidia_modeset(POE) intel_rapl_msr(E) intel_rapl_common(E) intel_uncore_frequency(E) intel_uncore_frequency_common(E) isst_if_common(E) sunrpc(E) skx_edac(E) nfit(E) libnvdimm(E) video(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) binfmt_misc(E) snd_hda_codec_realtek(E) joydev(E) irqbypass(E) rapl(E) intel_cstate(E) snd_hda_codec_generic(E) ledtrig_audio(E) snd_hda_codec_hdmi(E) snd_hda_intel(E) snd_intel_dspcfg(E) snd_intel_sdw_acpi(E) snd_hda_codec(E) snd_hda_core(E) snd_hwdep(E) snd_pcm(E)
[604223.580232] mei_wdt(E) rtsx_usb_ms(E) snd_timer(E) wdat_wdt(E) nvidia(POE) snd(E) think_lmi(E) intel_uncore(E) firmware_attributes_class(E) intel_wmi_thunderbolt(E) wmi_bmof(E) memstick(E) watchdog(E) soundcore(E) mei_me(E) mei(E) ioatdma(E) dca(E) evdev(E) msr(E) parport_pc(E) ppdev(E) lp(E) parport(E) tcp_bbr(E) drm(E) fuse(E) efi_pstore(E) configfs(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) btrfs(E) blake2b_generic(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) nls_ascii(E) nls_cp437(E) vfat(E) fat(E) dm_crypt(E) dm_mod(E) rtsx_usb_sdmmc(E) mmc_core(E) rtsx_usb(E) hid_generic(E) usbhid(E) hid(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) sha512_ssse3(E) sha512_generic(E) nvme(E) nvme_core(E) t10_pi(E) crc64_rocksoft_generic(E) ahci(E) libahci(E) xhci_pci(E) crc64_rocksoft(E) aesni_intel(E) crc_t10dif(E) libata(E) crct10dif_generic(E) xhci_hcd(E) crypto_simd(E) thinkpad_wmi(OE) crct10dif_pclmul(E) cryptd(E) pcspkr(E) intel_lpss_pci(E) crc64(E)
[604223.580428] i2c_i801(E) intel_lpss(E) crct10dif_common(E) e1000e(E) i2c_smbus(E) usbcore(E) scsi_mod(E) idma64(E) scsi_common(E) usb_common(E) wmi(E) button(E) [last unloaded: kvm(OE)]
[604223.580508] ---[ end trace 0000000000000000 ]---
[604223.656393] RIP: 0010:__kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.656691] Code: cc cc cc 4c 89 e0 48 2b 86 b0 00 00 00 48 3b 86 b8 00 00 00 48 19 c9 48 21 c8 48 c1 e0 0c 48 03 86 f8 00 00 00 49 89 c5 eb 8c <0f> 0b 0f 0b 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90
[604223.656700] RSP: 0018:ffffbfe943313b98 EFLAGS: 00010246
[604223.656711] RAX: 0000000000000000 RBX: 0000000000000002 RCX: ffff9decd2a4bf80
[604223.656718] RDX: 000000000080005f RSI: 0000000000000000 RDI: ffffbfe9425bd000
[604223.656725] RBP: 0000000000000002 R08: 0000000000000000 R09: 0000000000000002
[604223.656731] R10: 00000000ffffffff R11: ffff9decc8ca8290 R12: 000000000080005f
[604223.656738] R13: ffff9decd2a4bf80 R14: ffff9decc8ca8000 R15: 0000000000000000
[604223.656745] FS: 00007f548fc836c0(0000) GS:ffff9dfc00080000(0000) knlGS:0000000000000000
[604223.656754] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[604223.656761] CR2: 0000000013365000 CR3: 0000000b741fe002 CR4: 00000000003726e0
[604223.737599] RIP: 0010:__kvm_write_guest_page+0xc6/0xd0 [kvm]
[604223.737880] Code: cc cc cc 4c 89 e0 48 2b 86 b0 00 00 00 48 3b 86 b8 00 00 00 48 19 c9 48 21 c8 48 c1 e0 0c 48 03 86 f8 00 00 00 49 89 c5 eb 8c <0f> 0b 0f 0b 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90
[604223.737890] RSP: 0018:ffffbfe943313b98 EFLAGS: 00010246
[604223.737900] RAX: 0000000000000000 RBX: 0000000000000002 RCX: ffff9decd2a4bf80
[604223.737905] RDX: 000000000080005f RSI: 0000000000000000 RDI: ffffbfe9425bd000
[604223.737910] RBP: 0000000000000002 R08: 0000000000000000 R09: 0000000000000002
[604223.737914] R10: 00000000ffffffff R11: ffff9decc8ca8290 R12: 000000000080005f
[604223.737919] R13: ffff9decd2a4bf80 R14: ffff9decc8ca8000 R15: 0000000000000000
[604223.737925] FS: 00007f549048b6c0(0000) GS:ffff9dfbfff00000(0000) knlGS:0000000000000000
[604223.737934] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[604223.737941] CR2: 0000000012c00000 CR3: 0000000b741fe003 CR4: 00000000003726e0
[604224.943222] MainLoopThread[1928634]: segfault at 98 ip 00007f54c04fdcd0 sp 00007f539836c198 error 4 in libgfxstream_backend.so[7f54c04dc000+9ac000] likely on CPU 5 (core 5, socket 0)
[604224.943271] MainLoopThread[1928670]: segfault at 150 ip 00007f54c04fdcd0 sp 00007f539391d198 error 4
[604224.943274] Code: d8 49 c1 eb 38 49 83 fb 01 77 09 4d 8d 41 ff 49 21 c8 eb 13 49 89 c8 4c 39 c9 72 0b 48 89 c8 31 d2 49 f7 f1 49 89 d0 48 8b 07 <4a> 8b 04 c0 48 85 c0 0f 84 92 00 00 00 48 8b 30 48 85 f6 0f 84 86
[604224.943308] in libgfxstream_backend.so[7f54c04dc000+9ac000] likely on CPU 9 (core 3, socket 0)
[604224.943329] Code: d8 49 c1 eb 38 49 83 fb 01 77 09 4d 8d 41 ff 49 21 c8 eb 13 49 89 c8 4c 39 c9 72 0b 48 89 c8 31 d2 49 f7 f1 49 89 d0 48 8b 07 <4a> 8b 04 c0 48 85 c0 0f 84 92 00 00 00 48 8b 30 48 85 f6 0f 84 86
[604224.943333] MainLoopThread[1928647]: segfault at 118 ip 00007f54c04fdcd0 sp 00007f5394bb3198 error 4
[604224.943337] MainLoopThread[1928635]: segfault at 148 ip 00007f54c04fdcd0 sp 00007f539816b198 error 4 in libgfxstream_backend.so[7f54c04dc000+9ac000]
[604224.943354] in libgfxstream_backend.so[7f54c04dc000+9ac000]
[604224.943355] MainLoopThread[1928666]: segfault at 150 ip 00007f54c04fdcd0 sp 00007f539431e198 error 4
[604224.943361] likely on CPU 4 (core 4, socket 0)
[604224.943367] likely on CPU 10 (core 4, socket 0)

bo...@google.com <bo...@google.com> #90Oct 2, 2023 04:42PM

[ 319.876635] kvm_intel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and

https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
[ 335.237282] bad address 0xffffa07e00000000
[ 520.197432] bad address 0xffffa07e00000000
[ 520.197433] bad address 0xffffa07e00000000

qemu-maps.txt

157 KB

View

Download

bo...@google.com <bo...@google.com> #91Oct 2, 2023 05:26PM

btw, I reverted

https://github.com/torvalds/linux/commit/f8be156be163a052a067306417cd0ff679068c97 and it does not seems to help

the bad address at kvm_is_error_hva, and it is strange, given that the address looks like kernel space address 0xfff...
and the qemu memeory maps has no such address at all

ya...@google.com <ya...@google.com> Oct 2, 2023 05:57PM

Reassigned to ya...@google.com.

ya...@google.com <ya...@google.com> #92Oct 2, 2023 06:00PM

Andrew was unable to repro this issue. I will take it over for now (will probably sync up with Bo and Haitao offline)

hs...@google.com <hs...@google.com> #93Oct 3, 2023 05:14PM

Hi, Bo,
Is the "bad address" an HVA? In KVM, some HVA (and some guest physical address, too) is chosen to indicate an error. We need to double check whether 0xffffa07e00000000 simply means an error.

bo...@google.com <bo...@google.com> #94Oct 3, 2023 09:35PM

we found a page fault in the middle of ram.img address space,
you can try the following to disasble QuickbootFileBacked and see if that can work around the kvm bad address for now
-feature -QuickbootFileBacked

bo...@google.com <bo...@google.com> #95Oct 3, 2023 10:34PM

what appears to happen is that initially, we created a file (ram.img) backed memory mapping, which is continuous and have
the same size of ramSize (due to QuickbootFileBacked feature)

then, in themiddle of running emulator, somewhere munmap came an unmapped a few pages of that continous memory;
which then lead to kvm page fault.

disabling QuickbootFileBacked might mitigate this problem, but the root cause is to find the offending munmap and fix it.

bo...@google.com <bo...@google.com> #96Oct 4, 2023 01:53PM

another bad address, this time it has nothing to do with QuickbootFilebacked feature

Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000c0000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x0000000000000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000000c0000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000000c0000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x0000000000000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000000d0000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x0000000000000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000000d0000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x0000000000000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000c0000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x0000000000000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000c0000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x0000000000000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000000c0000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x0000000000000000, flags=0x00000000
Set : GPA = 0x0000000000000000 HVA=0x00007ff4b4800000, size=0x00000000000c0000, flags=0x00000000

---------- Start of EFAULT Debugging Info ----------
faulting guest physical address 0x000000002048d000
Found host virtual address of the faulting gpa 0x00007ff4d4c8d000
Printing /proc/self/maps...

7ff4b4700000-7ff4b4800000 rw-p 00000000 00:00 0
7ff4b4800000-7ff4d4c8d000 rw-p 00000000 00:00 0
7ff4d4c8f000-7ff574800000 rw-p 00000000 00:00 0
7ff574800000-7ff574801000 ---p 00000000 00:00 0
7ff574801000-7ff574803000 rw-s 00000000 00:05 748 /dev/nvidiactl
7ff574803000-7ff574807000 rw-s 00000000 00:05 748 /dev/nvidiactl
7ff574807000-7ff574808000 rw-s 00000000 00:05 750 /dev/nvidia0
7ff574808000-7ff57480a000 rw-s 00000000 00:05 748 /dev/nvidiactl
7ff57480a000-7ff57480b000 rw-s 00000000 00:05 750 /dev/nvidia0
7ff57480b000-7ff57480c000 rw-s 00000000 00:05 750 /dev/nvidia0
7ff57480c000-7ff57480d000 ---p 00000000 00:00 0
7ff57480d000-7ff57480f000 rw-p 00000000 00:00 0
7ff57480f000-7ff574811000 ---p 00000000 00:00 0

bo...@google.com <bo...@google.com> #97Oct 4, 2023 02:06PM

initially there is 3G mapping from 7ff4b4800000 to 7ff574800000,
then some unmap operation came along and punch a hole of 8192 bytes at
7ff4d4c8d000 to 7ff4d4c8f000

7ff4b4800000-7ff4d4c8d000 rw-p 00000000 00:00 0
7ff4d4c8f000-7ff574800000 rw-p 00000000 00:00 0

hs...@google.com <hs...@google.com> #98Oct 4, 2023 03:47PM

OK. So file-backed ram is irrelevant.

bo...@google.com <bo...@google.com> #99Oct 4, 2023 04:51PM

in addition, I don't think the hole is caused by munmap,

I traced the munmap, and it does not touch the hole at all.

btw, the ram.img is not mapped by mmap nither.

so, it probably is due to qemu itself.

st...@gmail.com <st...@gmail.com> #100Oct 5, 2023 05:53AM

Hi, I have the same problem both on amd radon 6650xt and integrate intel graphics card.
I confirm that flag -Vulkan resolve the issue.
What does this option do? Does it disable Vulkan?

ya...@google.com <ya...@google.com> #101Oct 5, 2023 05:17PM

Hi,

-feature -Vulkan disables Vulkan.

bo...@google.com <bo...@google.com> #102Oct 6, 2023 04:17PM

re #100,

when that happens, could you keep emulator alive (guest hangs but emulator still alive) and do the following
grep ram.img /proc/`pgrep qemu`/maps

I want to confirm you run into the same issue as I do here

bo...@google.com <bo...@google.com> #103Oct 6, 2023 05:40PM

it seems the gfxstream thread is punching the hole here:

MainLoopThread-2043089 [003] 348786.632249: sys_enter_munmap: addr: 0x7fa66a367000, len: 0x00002000
MainLoopThread-2043089 [003] 348786.632439: sys_exit_munmap: 0x0
this unmapped two pages here: 7fa6526b8000-7fa66a367000 rw-s 00000000 fe:01 589 /usr/local/google/home/bohu/.android/avd/fold.avd/snapshots/default_boot/ram.img
7fa66a369000-7fa7126b8000 rw-s 17cb1000 fe:01 589 /usr/local/google/home/bohu/.android/avd/fold.avd/snapshots/default_boot/ram.img

it is our MainLoopThread

guest/GoldfishAddressSpace/include/goldfish_address_space_android.impl: ::munmap(ptr, size);
guest/GoldfishAddressSpace/include/goldfish_address_space_android.impl: ::munmap(pagePtr, size);
guest/OpenglCodecCommon/goldfish_dma.cpp: munmap(reinterpret_cast<void *>(cxt->mapped_addr), cxt->size);
guest/OpenglSystemCommon/VirtioGpuPipeStream.cpp: munmap(m_virtio_mapped, kTransferBufferSize);
guest/platform/linux/VirtGpuBlobMapping.cpp: munmap(mPtr, mSize);
guest/profiler/perfetto.cpp: int res = munmap(start, outer_size);
guest/profiler/perfetto.cpp: munmap(start(), size());
we have a bunch of munmap in gfxstream

hs...@google.com <hs...@google.com> #104Oct 6, 2023 08:40PM

When I tied to reproduce the Bo's bug, I got a crash. But unlike the "kvm bad address", I got Segmentation fault. This can happen as soon as I see the launcher screen. Sometime I launch Chrome and trigger this crash. Sometime I need to run hours of CtsWindowManagerDeviceTestCases before I get the crash.

Although it looks like a different issue from Bo's. But it is also a memory issue.

I caught it using gdb. Due to my gdb issue, I cannot do source code level debugging. But I can use assembly to locate the source line. See below.

******************** Source Code**********************************************
void reservedunmarshal_VkPhysicalDeviceFeatures2(
VulkanStream* vkStream,
VkStructureType rootType,
VkPhysicalDeviceFeatures2* forUnmarshaling,
uint8_t** ptr)
{
memcpy((VkStructureType*)&forUnmarshaling->sType, *ptr, sizeof(VkStructureType));
*ptr += sizeof(VkStructureType);
if (rootType == VK_STRUCTURE_TYPE_MAX_ENUM)
{
rootType = forUnmarshaling->sType;
}
uint32_t pNext_size;
memcpy((uint32_t*)&pNext_size, *ptr, sizeof(uint32_t));
android::base::Stream::fromBe32((uint8_t*)&pNext_size);
*ptr += sizeof(uint32_t);
forUnmarshaling->pNext = nullptr;
if (pNext_size)
{
vkStream->alloc((void**)&forUnmarshaling->pNext, sizeof(VkStructureType));
memcpy((void*)forUnmarshaling->pNext, *ptr, sizeof(VkStructureType));
*ptr += sizeof(VkStructureType);
VkStructureType extType = *(VkStructureType*)(forUnmarshaling->pNext);
vkStream->alloc((void**)&forUnmarshaling->pNext, goldfish_vk_extension_struct_size_with_stream_features(vkStream->getFeatureBits(), rootType, forUnmarshaling->pNext));
----> *(VkStructureType*)forUnmarshaling->pNext = extType;
reservedunmarshal_extension_struct(vkStream, rootType, (void*)(forUnmarshaling->pNext), ptr);
}
reservedunmarshal_VkPhysicalDeviceFeatures(vkStream, rootType, (VkPhysicalDeviceFeatures*)(&forUnmarshaling->features), ptr);
}

**********************gdb output:******************************************

Thread 246 "MainLoopThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fa411154640 (LWP 228985)]
0x00007fa55dfbcaf8 in goldfish_vk::reservedunmarshal_VkPhysicalDeviceFeatures2(goldfish_vk::VulkanStream*, VkStructureType, VkPhysicalDeviceFeatures2*, unsigned char**) () from /home/tony/testemu/external/qemu/objs/distribution/emulator/lib64/libOpenglRender.so
(gdb) disas $rip
Dump of assembler code for function _ZN11goldfish_vk43reservedunmarshal_VkPhysicalDeviceFeatures2EPNS_12VulkanStreamE15VkStructureTypeP25VkPhysicalDeviceFeatures2PPh:
0x00007fa55dfbca50 <+0>: push %rbp
0x00007fa55dfbca51 <+1>: push %r15
0x00007fa55dfbca53 <+3>: push %r14
0x00007fa55dfbca55 <+5>: push %r13
0x00007fa55dfbca57 <+7>: push %r12
0x00007fa55dfbca59 <+9>: push %rbx
0x00007fa55dfbca5a <+10>: push %rax
0x00007fa55dfbca5b <+11>: mov %rcx,%rbx
0x00007fa55dfbca5e <+14>: mov %rdx,%r14
0x00007fa55dfbca61 <+17>: mov %esi,%r13d
0x00007fa55dfbca64 <+20>: mov %rdi,%r15
0x00007fa55dfbca67 <+23>: mov (%rcx),%rax
0x00007fa55dfbca6a <+26>: mov (%rax),%ebp
0x00007fa55dfbca6c <+28>: mov %ebp,(%rdx)
0x00007fa55dfbca6e <+30>: mov (%rcx),%rax
0x00007fa55dfbca71 <+33>: lea 0x4(%rax),%rcx
0x00007fa55dfbca75 <+37>: mov %rcx,(%rbx)
0x00007fa55dfbca78 <+40>: mov 0x4(%rax),%eax
0x00007fa55dfbca7b <+43>: mov %eax,0x4(%rsp)
0x00007fa55dfbca7f <+47>: lea 0x4(%rsp),%rdi
0x00007fa55dfbca84 <+52>: call 0x7fa55e7e8760 <_ZN7android4base6Stream8fromBe32EPh@plt>
0x00007fa55dfbca89 <+57>: addq $0x4,(%rbx)
0x00007fa55dfbca8d <+61>: movq $0x0,0x8(%r14)
0x00007fa55dfbca95 <+69>: cmpl $0x0,0x4(%rsp)
0x00007fa55dfbca9a <+74>: je 0x7fa55dfbcb08 <_ZN11goldfish_vk43reservedunmarshal_VkPhysicalDeviceFeatures2EPNS_12VulkanStreamE15VkStructureTypeP25VkPhysicalDeviceFeatures2PPh+184>
0x00007fa55dfbca9c <+76>: lea 0x8(%r14),%r12
0x00007fa55dfbcaa0 <+80>: cmp $0x7fffffff,%r13d
0x00007fa55dfbcaa7 <+87>: cmovne %r13d,%ebp
0x00007fa55dfbcaab <+91>: mov $0x4,%edx
0x00007fa55dfbcab0 <+96>: mov %r15,%rdi
0x00007fa55dfbcab3 <+99>: mov %r12,%rsi
0x00007fa55dfbcab6 <+102>: call 0x7fa55df5bd40
0x00007fa55dfbcabb <+107>: mov (%r12),%rax
0x00007fa55dfbcabf <+111>: mov (%rbx),%rcx
0x00007fa55dfbcac2 <+114>: mov (%rcx),%ecx
0x00007fa55dfbcac4 <+116>: mov %ecx,(%rax)
0x00007fa55dfbcac6 <+118>: addq $0x4,(%rbx)
0x00007fa55dfbcaca <+122>: mov (%r12),%rax
0x00007fa55dfbcace <+126>: mov (%rax),%r13d
0x00007fa55dfbcad1 <+129>: mov %r15,%rdi
0x00007fa55dfbcad4 <+132>: call 0x7fa55df5c4e0
0x00007fa55dfbcad9 <+137>: mov (%r12),%rdx
0x00007fa55dfbcadd <+141>: mov %eax,%edi
0x00007fa55dfbcadf <+143>: mov %ebp,%esi
0x00007fa55dfbcae1 <+145>: call 0x7fa55df68eb0 <_ZN11goldfish_vk54goldfish_vk_extension_struct_size_with_stream_featuresEj15VkStructureTypePKv>
0x00007fa55dfbcae6 <+150>: mov %r15,%rdi
0x00007fa55dfbcae9 <+153>: mov %r12,%rsi
0x00007fa55dfbcaec <+156>: mov %rax,%rdx
0x00007fa55dfbcaef <+159>: call 0x7fa55df5bd40
0x00007fa55dfbcaf4 <+164>: mov (%r12),%rdx
=> 0x00007fa55dfbcaf8 <+168>: mov %r13d,(%rdx)
0x00007fa55dfbcafb <+171>: mov %r15,%rdi
0x00007fa55dfbcafe <+174>: mov %ebp,%esi
0x00007fa55dfbcb00 <+176>: mov %rbx,%rcx
0x00007fa55dfbcb03 <+179>: call 0x7fa55dfb14a0 <_ZN11goldfish_vk34reservedunmarshal_extension_structEPNS_12VulkanStreamE15VkStructureTypePvPPh>
0x00007fa55dfbcb08 <+184>: add $0x10,%r14
0x00007fa55dfbcb0c <+188>: mov %r14,%rdx
0x00007fa55dfbcb0f <+191>: mov %rbx,%rcx
0x00007fa55dfbcb12 <+194>: call 0x7fa55dfb4ce0 <_ZN11goldfish_vk42reservedunmarshal_VkPhysicalDeviceFeaturesEPNS_12VulkanStreamE15VkStructureTypeP24VkPhysicalDeviceFeaturesPPh>
0x00007fa55dfbcb17 <+199>: add $0x8,%rsp
0x00007fa55dfbcb1b <+203>: pop %rbx
0x00007fa55dfbcb1c <+204>: pop %r12
0x00007fa55dfbcb1e <+206>: pop %r13
0x00007fa55dfbcb20 <+208>: pop %r14
0x00007fa55dfbcb22 <+210>: pop %r15
0x00007fa55dfbcb24 <+212>: pop %rbp
0x00007fa55dfbcb25 <+213>: ret
End of assembler dump.
(gdb) p $rip
$1 = (void (*)()) 0x7fa55dfbcaf8 <goldfish_vk::reservedunmarshal_VkPhysicalDeviceFeatures2(goldfish_vk::VulkanStream*, VkStructureType, VkPhysicalDeviceFeatures2*, unsigned char**)+168>
(gdb) p $rdx
$2 = 0
(gdb) p $r13d
$3 = 1000338000

ya...@google.com <ya...@google.com> #105Oct 6, 2023 08:51PM

Haitao,

what was your system image build and emulator build? We have a few changes recently that might affect the behavior of VkPhysicalDeviceFeatures2. It could be a recent regression.

hs...@google.com <hs...@google.com> #106Oct 6, 2023 08:57PM

git log shows the top is: Add support for SDK 14.0(XCode 15). This is a few Cls after "Bump emulator to 34.1.5"

System Image is API 34 Google Play image I downloaded yesterday.

ya...@google.com <ya...@google.com> #107Oct 6, 2023 09:05PM

Haitao,

For the google play image, did you download it from internal or external? Do you have the build id?

For the emulator, would you try to go to hardware/google/gfxstream, do a git log and see if you are before or after this one aosp/2768212 ?

ya...@google.com <ya...@google.com> #108Oct 6, 2023 09:06PM

Also, does it print anything like unknown structType

hs...@google.com <hs...@google.com> #109Oct 6, 2023 09:11PM

I downloaded from Android Studio. So it should be an external one. How do I check the buildid?
I will check gfxstream.

I did not see anything else from console. Just "Segmentation fault (core dumped)".

hs...@google.com <hs...@google.com> #110Oct 6, 2023 09:14PM

Yes. It is after 2768212. One CL after.

ya...@google.com <ya...@google.com> #111Oct 6, 2023 09:14PM

If you run this:

cat ~/Android/Sdk/system-images/android-34/google_apis/x86_64/build.prop

There should be a ro.build.id and a ro.build.display.id

ya...@google.com <ya...@google.com> #112Oct 6, 2023 09:14PM

Would you try to roll back to before 2768212?

hs...@google.com <hs...@google.com> #113Oct 6, 2023 09:16PM

ro.build.id=UE1A.230829.019

ro.build.display.id= UE1A.230829.019 dev-keys

hs...@google.com <hs...@google.com> #114Oct 6, 2023 09:17PM

I will roll back and see if helps.

hs...@google.com <hs...@google.com> #115Oct 6, 2023 09:25PM

Rolling back does not help.

ya...@google.com <ya...@google.com> #116Oct 6, 2023 10:09PM

Chat with Haitao offline regarding #104. gfxstream emulator works but non-gfxstream doesn't.

The non-gfxstream emulator does not support vk1.3, so please stick with the gfxstream build for newer Android U images.

bo...@google.com <bo...@google.com> #117Oct 9, 2023 06:03PM

we have a work around that basically checks and prevents such hole punching; if you want to try

https://ci.android.com/builds/submitted/10921799/emulator-linux_x64_gfxstream/latest/sdk-repo-linux-emulator-10921799.zip

ya...@google.com <ya...@google.com> Oct 11, 2023 06:43PM

Reassigned to bo...@google.com.

de...@gmail.com <de...@gmail.com> #118Oct 11, 2023 10:03PM

Comment has been deleted.

Message last modified on Oct 11, 2023 10:30PM

pa...@infocusp.com <pa...@infocusp.com> #119Oct 16, 2023 12:43PM

The emulator crashes for me as well, when I open the Chrome app.

Android Studio Giraffe | 2022.3.1 Patch 2
Build #AI-223.8836.35.2231.10811636, built on September 15, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 6.2.0-34-generic
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Registry:
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.experimental.ui=true

Non-Bundled Plugins:
    com.tabnine.TabNine (1.9.0)
    idea.plugin.protoeditor (223.8214.6)

Current Desktop: ubuntu:GNOME

Emulator version: 32.1.15
Android image: API 34 Google APIs x86_64

Message last modified on Oct 16, 2023 12:45PM

bo...@google.com <bo...@google.com> #120Oct 16, 2023 03:43PM

re #119, could you try

https://buganizer.corp.google.com/issues/225541819#comment117

also when it crashes, could you post the crash id here ?

va...@gmail.com <va...@gmail.com> #121Oct 16, 2023 08:33PM

This is still happening to me on a fresh install of Android Studio with Android API 34 loaded on the emulators and it's really annoying. I've tried a Pixel 7 emulator and a Pixel 5 emulator. Opening Chrome for the first time on a brand new virtual device crashes the entire virtual device and forcibly closes down.

What's worse is that when I went through the process of logging into a Google account on the virtual device, giving Chrome all permissions to use Photos, Mic, Location, etc, I clicked on Chrome, it opened fully, allowed me to select my account, and then it crashed and crashed the emulator. Now the entire Emulator crashes as soon as it starts without me opening anything or interacting with it lol.

The crashing behavior does not occur on API 33.

I'm running Windows 11 x64 with an Nvidia GPU
Android Studio Giraffe | 2022.3.1 Patch 2
Build #AI-223.8836.35.2231.10811636, built on September 14, 2023
Runtime version: 17.0.6+0-b2043.56-10027231 amd64

What files and information do you need to help fix this that I can provide from my machine? Do you have a template?

Message last modified on Oct 16, 2023 08:59PM

hs...@google.com <hs...@google.com> #122Oct 16, 2023 08:56PM

Reply to #121, your crash happened on Windows. So it is different from what we have discussed here. As Bo said above, do you have a crash id?
In addition, can you let us know your CPU model, memory size? Can you run the emulator from commandline "emulator.exe -avd <avd name> -verbose -show-kernel" and paste the output here?

va...@gmail.com <va...@gmail.com> #123Oct 16, 2023 11:44PM

Where can I find the crash IDs at? I don't see any crash ID or crash window when the emulator forcibly shuts down. I saw it once and I made a report but I haven't seen it since.

I attached the output of the emulator starting, it crashed after it started but it didn't make any mention of it in the log output. It crashed right after message [ 31.973264]

CPU Model: Intel Core i7-10700K
Memory: 16GBs of DDR4-3200 using XMP

Let me know if you need any other info

avdCrashOutput-AndroidAPI34-10-16-23.txt

239 KB

View

Download

bo...@google.com <bo...@google.com> #124Oct 17, 2023 12:34AM

Android emulator version 26.0.3.0 (build_id 3965150)
emulator:Found AVD name 'Pixel_5_API_34'
emulator:Found AVD target architecture: x86_6

this version is a bit outdated, could you try updating it to latest stable or canary ?

va...@gmail.com <va...@gmail.com> #125Oct 17, 2023 06:51PM

@ #124 Android Studio shows version 32.1.15 being installed as seen in my screen shot. I only installed Android Studio in the last 5 days from the latest release, I'm not sure where it would be finding 26.0.3.0 at. The SDK Manager gives no option to update the emulator. Maybe this is part of the issue?

Is there a newer binary you'd like me to try out and report back on that you can link me to?

AndroidEmulator-32.1.15-Installed.png

40 KB

View

Download

va...@gmail.com <va...@gmail.com> #126Oct 17, 2023 07:05PM

Just for reference, I downloaded 32.1.15 from here - https://developer.android.com/studio/emulator_archive; extracted it into a new folder and ran the same command as above emulator.exe -avd Pixel_5_API_34 -verbose -show-kernel

...

INFO | Android emulator version 32.1.15.0 (build_id 10696886) (CL:N/A)

It shows the correct version when launching but still crashes without any user input after Android boots up.

I attached the kernel log as well. Happy to test more stuff if it helps.

Message last modified on Oct 17, 2023 07:06PM

AndroidEmulator-32.1.15.0-StillCrashing.txt

234 KB

View

Download

hs...@google.com <hs...@google.com> #127Oct 17, 2023 08:06PM

Thanks for offering help in doing some experiments.
Can you check if adding "-feature -Vulkan" or "-feature -feature -GLDirectMem,-GLDMA,-GLDMA2" can solve your problem?

I had an AMD CPU and NVidia GPU but was not able to reproduce the issue. Note that all other reports in this bug are on Linux. It is hard to tell whether yours are the same one at the moment.

va...@gmail.com <va...@gmail.com> #128Oct 18, 2023 02:07AM

Ah interesting, so adding the flag -feature -Vulkan, the emulator seems to be stable. Opening Chrome seems okay but web pages do not render correctly. If I shutdown the emulator and start it up again without the Vulkan flag it crashes as soon as I click on Chrome.

.\emulator.exe -avd Pixel_5_API_34 -verbose -show-kernel -feature -Vulkan <-- Doesn't crash, Chrome opens okay but web pages do not render correctly, any site that tries to render shows up blank.

.\emulator.exe -avd Pixel_5_API_34 -verbose -show-kernel -feature -GLDirectMem <-- Crashes when clicking Chrome

.\emulator.exe -avd Pixel_5_API_34 -verbose -show-kernel -feature -GLDirectMem -feature -GLDMA <-- Crashes when clicking Chrome

.\emulator.exe -avd Pixel_5_API_34 -verbose -show-kernel -feature -GLDirectMem -feature -GLDMA -feature -GLDMA2 <-- Crashed before I clicked on Chrome

.\emulator.exe -avd Pixel_5_API_34 -verbose -show-kernel -feature -GLDirectMem -feature -GLDMA2 <-- Crashes when clicking Chrome

.\emulator.exe -avd Pixel_5_API_34 -verbose -show-kernel -feature -GLDirectMem -feature -GLDMA2 -feature -Vulkan <-- Chrome opens but won't render web pages, they show up blank.

Let me know if you want any other info or something else tested. Doesn't seem limited to only Linux :)

I have an Nvidia 3080 for reference.

Message last modified on Oct 18, 2023 02:17AM

va...@gmail.com <va...@gmail.com> #129Oct 18, 2023 02:22AM

Attached are images of how the web pages look with issues.

Screenshot_1697595358.png

50 KB

View

Download

Screenshot_1697595497.png

141 KB

View

Download

Screenshot_1697595713.png

699 KB

View

Download

gs...@gmail.com <gs...@gmail.com> #130Oct 18, 2023 06:54AM

Re #121, #122: On windows (at least for me) this issue of chrome immediately crashing started with the release of the 'Google APIs Intel x86_64 Atom System Image' API Level 34 revision 9. API 34 revision 10, that I got offered today, is also affected. Before that, i.e. up to and including API 34 revision 8 system image, this issue did NOT occur. It also des NOT occur on API 33 system images, up to and including the recent revision 15.

The emulator was in all those cases 32.1.15.

I've submitted an emulator crash report (as offered on the next emulator startup) and left a reference to this issue / comment 130 in the description.

If this issue here is only about linux (and started long time ago), would it make sense to split this windows related issue (which started only recently and seems to be api 34 system image related) off into a separate track?

hs...@google.com <hs...@google.com> #131Oct 18, 2023 04:39PM

Reassigned to ya...@google.com.

@yahan Can you take a look at the latest reports from users on Windows?

bo...@google.com <bo...@google.com> #132Oct 18, 2023 04:40PM

recent api34 image needs canary emulator that has better support of vulkan apis.

you can try the canary using canary studio
or some 33.1.17 here

https://developer.android.com/studio/emulator_archive

ya...@google.com <ya...@google.com> #133Oct 18, 2023 05:22PM

Hi,

if you are using API 34 system image revision 10, please either use -feature -Vulkan, or switch to the latest emulator version 33* or 34*. They are available with the Preview version of Android Studio https://developer.android.com/studio/preview.

de...@gmail.com <de...@gmail.com> #134Oct 19, 2023 10:09PM

This issue persists on Windows 11 including emulator v10

ca...@google.com <ca...@google.com> #135Oct 31, 2023 10:51PM

On emu 34.1.9-11009885 and Windows. When I run API 33 on swifthshader opening chrome crashes the AVD for me.

verbose.txt

169 KB

View

Download

Screen Recording 2023-10-31 at 3.48.49 PM.mov

26 MB

Download

cl...@gmail.com <cl...@gmail.com> #136Nov 14, 2023 04:00PM

Same happens to me on Windows 11 23H2 with i5-11400F and GTX1660 Super (using latest driver 546.17). Using Android Studio Giraffe 2022.3.1 Patch 3, Emulator 32.1.15 running Android 14. Issue is gone when using the Vulkan flag but I don't want to do this everytime I want to start my emulator.

ta...@gmail.com <ta...@gmail.com> #137Dec 3, 2023 03:45PM

-verbose -show-kernel -feature -Vulkan

open chrome runing ok.

crash when open chrome in the AVD

./Sdk/emulator/emulator -avd Pixel_7_Pro_API_34 -verbose -show-kernel
INFO    | Storing crashdata in: /tmp/android-takeseem/emu-crash-34.1.10.db, detection is enabled for process: 61527
INFO    | Android emulator version 34.1.10.0 (build_id 11042718) (CL:N/A)
DEBUG   | Current emulator version 34.1.10 is the same as the required version 34.1.10.
INFO    | Deleting /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/bootcompleted.ini done
INFO    | Found AVD name 'Pixel_7_Pro_API_34'
INFO    | Found AVD target architecture: x86_64
INFO    | argv[0]: './Sdk/emulator/emulator'; program directory: '/data/app/android/Android/Sdk/emulator'
INFO    | Found systemPath /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64/
INFO    | emuDirName: '/data/app/android/Android/Sdk/emulator'
INFO    | try dir /data/app/android/Android/Sdk/emulator
INFO    | Trying emulator path '/data/app/android/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64'
INFO    | Found target-specific 64-bit emulator binary: /data/app/android/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64
INFO    | Adding library search path: '/data/app/android/Android/Sdk/emulator/lib64'
INFO    | Adding library search path: '/data/app/android/Android/Sdk/emulator/lib64/gles_swiftshader'
INFO    | Adding library search path: '/data/app/android/Android/Sdk/emulator/lib64/libstdc++'
DEBUG   | emulator: Running :/data/app/android/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64
DEBUG   | qemu backend: argv[00] = "/data/app/android/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64"
DEBUG   | qemu backend: argv[01] = "-avd"
DEBUG   | qemu backend: argv[02] = "Pixel_7_Pro_API_34"
DEBUG   | qemu backend: argv[03] = "-verbose"
DEBUG   | qemu backend: argv[04] = "-show-kernel"
DEBUG   | Concatenated backend parameters:  /data/app/android/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64 -avd Pixel_7_Pro_API_34 -verbose -show-kernel
INFO    | Storing crashdata in: /tmp/android-takeseem/emu-crash-34.1.10.db, detection is enabled for process: 61527
INFO    | Duplicate loglines will be removed, if you wish to see each individual line launch with the -log-nofilter flag.
DEBUG   | autoconfig: -skin pixel_7_pro
DEBUG   | autoconfig: -skindir /home/takeseem/Android/Sdk/skins/
DEBUG   | autoconfig: -kernel /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//kernel-ranchu
DEBUG   | Target arch = 'x86_64'
DEBUG   | Auto-detect: Kernel image requires new device naming scheme.
DEBUG   | Auto-detect: Kernel does not support YAFFS2 partitions.
DEBUG   | autoconfig: -ramdisk /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//ramdisk.img
DEBUG   | Using initial system image: /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//system.img
DEBUG   | Using initial vendor image: /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//vendor.img
DEBUG   | autoconfig: -data /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/userdata-qemu.img
DEBUG   | autoconfig: -initdata /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/userdata.img
DEBUG   | autoconfig: -cache /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/cache.img
DEBUG   | autoconfig: -sdcard /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/sdcard.img
DEBUG   | foldable or large screen devices with api >=33 is set to have minimum ram 3G
INFO    | Increasing RAM size to 3072MB
DEBUG   | VM heap size 384MB is below hardware specified minimum of 576MB,setting it to that value
DEBUG   | System image is read only
DEBUG   | Found 1 DNS servers:
DEBUG   | 	127.0.0.53
DEBUG   | Starting hostapd main loop.
DEBUG   | trying to load skin file '/home/takeseem/Android/Sdk/skins//pixel_7_pro/layout'
DEBUG   | File System is ext4, do not disable QuickbootFileBacked feature
DEBUG   | statvfs('/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/snapshots/default_boot/ram.img') failed: No such file or directory
DEBUG   | CPU Acceleration: working
DEBUG   | CPU Acceleration status: KVM (version 12) is installed and usable.
DEBUG   | handleCpuAcceleration: feature check for hvf
DEBUG   | Bluetooth requested by guest
DEBUG   | started modem simulator host server at port: 37603
library_mode host gpu mode host
DEBUG   | GPU emulation enabled using 'host' mode
DEBUG   | Initializing hardware OpenGLES emulation support
I1203 23:52:09.207024   61527 HealthMonitor.cpp:279] HealthMonitor disabled.
DEBUG   | create display 0
DEBUG   | setDisplayPose 0 x 0 y 0 w 1440 h 3120 dpi 0
cannot add library libvulkan.so: failed
added library libvulkan.so.1
createGlobalVkEmulation:964 Selecting Vulkan device: AMD Unknown (RADV GFX1103_R1)
initialize: Supports id properties, got a vulkan device UUID
WARNING: could not open libX11.so, try libX11.so.6
I1203 23:52:09.312144   61527 VkCommonOperations.cpp:1226] Initializing VkEmulation features:
I1203 23:52:09.312160   61527 VkCommonOperations.cpp:1227]     glInteropSupported: true
I1203 23:52:09.312163   61527 VkCommonOperations.cpp:1228]     useDeferredCommands: true
I1203 23:52:09.312167   61527 VkCommonOperations.cpp:1230]     createResourceWithRequirements: true
I1203 23:52:09.312170   61527 VkCommonOperations.cpp:1231]     useVulkanComposition: false
I1203 23:52:09.312173   61527 VkCommonOperations.cpp:1232]     useVulkanNativeSwapchain: false
I1203 23:52:09.312176   61527 VkCommonOperations.cpp:1233]     enable guestRenderDoc: false
I1203 23:52:09.312179   61527 VkCommonOperations.cpp:1234]     ASTC LDR emulation mode: 2
I1203 23:52:09.312182   61527 VkCommonOperations.cpp:1235]     enable ETC2 emulation: true
I1203 23:52:09.312185   61527 VkCommonOperations.cpp:1236]     enable Ycbcr emulation: false
I1203 23:52:09.312188   61527 VkCommonOperations.cpp:1237]     guestUsesAngle: false
I1203 23:52:09.312190   61527 VkCommonOperations.cpp:1238]     useDedicatedAllocations: true
I1203 23:52:09.312361   61527 FrameBuffer.cpp:486] Graphics Adapter Vendor Google (AMD)
I1203 23:52:09.312366   61527 FrameBuffer.cpp:487] Graphics Adapter Android Emulator OpenGL ES Translator (GFX1103_R1 (gfx1103_r1, LLVM 15.0.7, DRM 3.49, 6.2.0-37-generic))
I1203 23:52:09.312370   61527 FrameBuffer.cpp:488] Graphics API Version OpenGL ES 3.0 (4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1)
I1203 23:52:09.312373   61527 FrameBuffer.cpp:489] Graphics API Extensions GL_OES_EGL_sync GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_depth24 GL_OES_depth32 GL_OES_element_index_uint GL_OES_texture_float GL_OES_texture_float_linear GL_OES_compressed_paletted_texture GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_packed_depth_stencil GL_OES_vertex_half_float GL_OES_texture_npot GL_OES_rgb8_rgba8 GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_texture_format_BGRA8888 GL_APPLE_texture_format_BGRA8888 
I1203 23:52:09.312377   61527 FrameBuffer.cpp:490] Graphics Device Extensions N/A
INFO    | Setting vsync to 60 hz
DEBUG   | Found 1 DNS servers:
DEBUG   | 	127.0.0.53
INFO    | Content of hardware configuration file:
INFO    | 	hw.cpu.arch = x86_64
INFO    | 	hw.cpu.ncore = 4
INFO    | 	hw.ramSize = 3072
INFO    | 	hw.screen = multi-touch
INFO    | 	hw.mainKeys = false
INFO    | 	hw.trackBall = false
INFO    | 	hw.keyboard = true
INFO    | 	hw.keyboard.lid = false
INFO    | 	hw.keyboard.charmap = qwerty2
INFO    | 	hw.dPad = false
INFO    | 	hw.rotaryInput = false
INFO    | 	hw.gsmModem = true
INFO    | 	hw.gps = true
INFO    | 	hw.battery = true
INFO    | 	hw.accelerometer = true
INFO    | 	hw.accelerometer_uncalibrated = true
INFO    | 	hw.gyroscope = true
INFO    | 	hw.audioInput = true
INFO    | 	hw.audioOutput = true
INFO    | 	hw.sdCard = true
INFO    | 	hw.sdCard.path = /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/sdcard.img
INFO    | 	disk.cachePartition = true
INFO    | 	disk.cachePartition.path = /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/cache.img
INFO    | 	disk.cachePartition.size = 66m
INFO    | 	test.quitAfterBootTimeOut = -1
INFO    | 	test.delayAdbTillBootComplete = 0
INFO    | 	test.monitorAdb = 0
INFO    | 	hw.lcd.width = 1440
INFO    | 	hw.lcd.height = 3120
INFO    | 	hw.lcd.depth = 16
INFO    | 	hw.lcd.circular = false
INFO    | 	hw.lcd.density = 560
INFO    | 	hw.lcd.backlight = true
INFO    | 	hw.lcd.vsync = 60
INFO    | 	hw.gltransport = pipe
INFO    | 	hw.gltransport.asg.writeBufferSize = 1048576
INFO    | 	hw.gltransport.asg.writeStepSize = 4096
INFO    | 	hw.gltransport.asg.dataRingSize = 32768
INFO    | 	hw.gltransport.drawFlushInterval = 800
INFO    | 	hw.displayRegion.0.1.xOffset = -1
INFO    | 	hw.displayRegion.0.1.yOffset = -1
INFO    | 	hw.displayRegion.0.1.width = 0
INFO    | 	hw.displayRegion.0.1.height = 0
INFO    | 	hw.displayRegion.0.2.xOffset = -1
INFO    | 	hw.displayRegion.0.2.yOffset = -1
INFO    | 	hw.displayRegion.0.2.width = 0
INFO    | 	hw.displayRegion.0.2.height = 0
INFO    | 	hw.displayRegion.0.3.xOffset = -1
INFO    | 	hw.displayRegion.0.3.yOffset = -1
INFO    | 	hw.displayRegion.0.3.width = 0
INFO    | 	hw.displayRegion.0.3.height = 0
INFO    | 	hw.display1.width = 0
INFO    | 	hw.display1.height = 0
INFO    | 	hw.display1.density = 0
INFO    | 	hw.display1.xOffset = -1
INFO    | 	hw.display1.yOffset = -1
INFO    | 	hw.display1.flag = 0
INFO    | 	hw.display2.width = 0
INFO    | 	hw.display2.height = 0
INFO    | 	hw.display2.density = 0
INFO    | 	hw.display2.xOffset = -1
INFO    | 	hw.display2.yOffset = -1
INFO    | 	hw.display2.flag = 0
INFO    | 	hw.display3.width = 0
INFO    | 	hw.display3.height = 0
INFO    | 	hw.display3.density = 0
INFO    | 	hw.display3.xOffset = -1
INFO    | 	hw.display3.yOffset = -1
INFO    | 	hw.display3.flag = 0
INFO    | 	hw.multi_display_window = false
INFO    | 	hw.hotplug_multi_display = false
INFO    | 	hw.gpu.enabled = true
INFO    | 	hw.gpu.mode = host
INFO    | 	hw.initialOrientation = Portrait
INFO    | 	hw.camera.back = virtualscene
INFO    | 	hw.camera.front = emulated
INFO    | 	vm.heapSize = 576
INFO    | 	hw.sensors.light = true
INFO    | 	hw.sensors.pressure = true
INFO    | 	hw.sensors.humidity = true
INFO    | 	hw.sensors.proximity = true
INFO    | 	hw.sensors.magnetic_field = true
INFO    | 	hw.sensors.magnetic_field_uncalibrated = true
INFO    | 	hw.sensors.gyroscope_uncalibrated = true
INFO    | 	hw.sensors.orientation = true
INFO    | 	hw.sensors.temperature = true
INFO    | 	hw.sensors.rgbclight = false
INFO    | 	hw.sensor.hinge = false
INFO    | 	hw.sensor.hinge.count = 0
INFO    | 	hw.sensor.hinge.type = 0
INFO    | 	hw.sensor.hinge.sub_type = 0
INFO    | 	hw.sensor.hinge.fold_to_displayRegion.0.1_at_posture = 1
INFO    | 	hw.sensor.roll = false
INFO    | 	hw.sensor.roll.count = 0
INFO    | 	hw.sensor.roll.resize_to_displayRegion.0.1_at_posture = 6
INFO    | 	hw.sensor.roll.resize_to_displayRegion.0.2_at_posture = 6
INFO    | 	hw.sensor.roll.resize_to_displayRegion.0.3_at_posture = 6
INFO    | 	hw.sensors.heart_rate = false
INFO    | 	hw.sensors.wrist_tilt = false
INFO    | 	hw.useext4 = true
INFO    | 	hw.arc = false
INFO    | 	hw.arc.autologin = false
INFO    | 	hw.device.name = pixel_7_pro
INFO    | 	kernel.path = /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//kernel-ranchu
INFO    | 	kernel.newDeviceNaming = yes
INFO    | 	kernel.supportsYaffs2 = no
INFO    | 	disk.ramdisk.path = /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//ramdisk.img
INFO    | 	disk.systemPartition.initPath = /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//system.img
INFO    | 	disk.systemPartition.size = 2957m
INFO    | 	disk.vendorPartition.initPath = /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//vendor.img
INFO    | 	disk.vendorPartition.size = 800m
INFO    | 	disk.dataPartition.path = /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/userdata-qemu.img
INFO    | 	disk.dataPartition.size = 6g
INFO    | 	disk.encryptionKeyPartition.path = /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/encryptionkey.img
INFO    | 	PlayStore.enabled = true
INFO    | 	avd.name = Pixel_7_Pro_API_34
INFO    | 	avd.id = Pixel_7_Pro_API_34
INFO    | 	fastboot.forceColdBoot = false
INFO    | 	userdata.useQcow2 = true
INFO    | 	firstboot.bootFromDownloadableSnapshot = true
INFO    | 	firstboot.bootFromLocalSnapshot = true
INFO    | 	firstboot.saveToLocalSnapshot = true
INFO    | 	android.sdk.root = /data/app/android/Android/Sdk
INFO    | 	android.avd.home = /home/takeseem/.android/avd
INFO    | .
INFO    | QEMU options list:
INFO    | 	 argv[00] = "/data/app/android/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64"
INFO    | 	 argv[01] = "-dns-server"
INFO    | 	 argv[02] = "127.0.0.53"
INFO    | 	 argv[03] = "-mem-path"
INFO    | 	 argv[04] = "/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/snapshots/default_boot/ram.img"
INFO    | 	 argv[05] = "-mem-file-shared"
INFO    | 	 argv[06] = "-serial"
INFO    | 	 argv[07] = "stdio"
INFO    | 	 argv[08] = "-device"
INFO    | 	 argv[09] = "goldfish_pstore,addr=0xff018000,size=0x10000,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/data/misc/pstore/pstore.bin"
INFO    | 	 argv[10] = "-cpu"
INFO    | 	 argv[11] = "android64-xts"
INFO    | 	 argv[12] = "-enable-kvm"
INFO    | 	 argv[13] = "-smp"
INFO    | 	 argv[14] = "cores=4"
INFO    | 	 argv[15] = "-m"
INFO    | 	 argv[16] = "3072"
INFO    | 	 argv[17] = "-lcd-density"
INFO    | 	 argv[18] = "560"
INFO    | 	 argv[19] = "-object"
INFO    | 	 argv[20] = "iothread,id=disk-iothread"
INFO    | 	 argv[21] = "-nodefaults"
INFO    | 	 argv[22] = "-kernel"
INFO    | 	 argv[23] = "/data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//kernel-ranchu"
INFO    | 	 argv[24] = "-initrd"
INFO    | 	 argv[25] = "/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/initrd"
INFO    | 	 argv[26] = "-drive"
INFO    | 	 argv[27] = "if=none,index=0,id=system,if=none,file=/data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//system.img,read-only"
INFO    | 	 argv[28] = "-device"
INFO    | 	 argv[29] = "virtio-blk-pci,drive=system,iothread=disk-iothread,modern-pio-notify"
INFO    | 	 argv[30] = "-drive"
INFO    | 	 argv[31] = "if=none,index=1,id=cache,if=none,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/cache.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576"
INFO    | 	 argv[32] = "-device"
INFO    | 	 argv[33] = "virtio-blk-pci,drive=cache,iothread=disk-iothread,modern-pio-notify"
INFO    | 	 argv[34] = "-drive"
INFO    | 	 argv[35] = "if=none,index=2,id=userdata,if=none,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/userdata-qemu.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576"
INFO    | 	 argv[36] = "-device"
INFO    | 	 argv[37] = "virtio-blk-pci,drive=userdata,iothread=disk-iothread,modern-pio-notify"
INFO    | 	 argv[38] = "-drive"
INFO    | 	 argv[39] = "if=none,index=3,id=encrypt,if=none,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/encryptionkey.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576"
INFO    | 	 argv[40] = "-device"
INFO    | 	 argv[41] = "virtio-blk-pci,drive=encrypt,iothread=disk-iothread,modern-pio-notify"
INFO    | 	 argv[42] = "-drive"
INFO    | 	 argv[43] = "if=none,index=4,id=vendor,if=none,file=/data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//vendor.img,read-only"
INFO    | 	 argv[44] = "-device"
INFO    | 	 argv[45] = "virtio-blk-pci,drive=vendor,iothread=disk-iothread,modern-pio-notify"
INFO    | 	 argv[46] = "-drive"
INFO    | 	 argv[47] = "if=none,index=5,id=sdcard,if=none,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/sdcard.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576"
INFO    | 	 argv[48] = "-device"
INFO    | 	 argv[49] = "virtio-blk-pci,drive=sdcard,iothread=disk-iothread,modern-pio-notify"
INFO    | 	 argv[50] = "-netdev"
INFO    | 	 argv[51] = "user,id=mynet"
INFO    | 	 argv[52] = "-device"
INFO    | 	 argv[53] = "virtio-net-pci,netdev=mynet"
INFO    | 	 argv[54] = "-chardev"
INFO    | 	 argv[55] = "null,id=forhvc0"
INFO    | 	 argv[56] = "-chardev"
INFO    | 	 argv[57] = "null,id=forhvc1"
INFO    | 	 argv[58] = "-device"
INFO    | 	 argv[59] = "virtio-serial-pci,ioeventfd=off"
INFO    | 	 argv[60] = "-device"
INFO    | 	 argv[61] = "virtconsole,chardev=forhvc0"
INFO    | 	 argv[62] = "-device"
INFO    | 	 argv[63] = "virtconsole,chardev=forhvc1"
INFO    | 	 argv[64] = "-chardev"
INFO    | 	 argv[65] = "netsim,id=bluetooth"
INFO    | 	 argv[66] = "-device"
INFO    | 	 argv[67] = "virtserialport,chardev=bluetooth,name=bluetooth"
INFO    | 	 argv[68] = "-device"
INFO    | 	 argv[69] = "virtio-serial,ioeventfd=off"
INFO    | 	 argv[70] = "-chardev"
INFO    | 	 argv[71] = "socket,port=36775,host=::1,nowait,nodelay,reconnect=10,ipv6,id=modem"
INFO    | 	 argv[72] = "-device"
INFO    | 	 argv[73] = "virtserialport,chardev=modem,name=modem"
INFO    | 	 argv[74] = "-device"
INFO    | 	 argv[75] = "virtio-rng-pci"
INFO    | 	 argv[76] = "-show-cursor"
INFO    | 	 argv[77] = "-device"
INFO    | 	 argv[78] = "virtio_input_multi_touch_pci_1"
INFO    | 	 argv[79] = "-device"
INFO    | 	 argv[80] = "virtio_input_multi_touch_pci_2"
INFO    | 	 argv[81] = "-device"
INFO    | 	 argv[82] = "virtio_input_multi_touch_pci_3"
INFO    | 	 argv[83] = "-device"
INFO    | 	 argv[84] = "virtio_input_multi_touch_pci_4"
INFO    | 	 argv[85] = "-device"
INFO    | 	 argv[86] = "virtio_input_multi_touch_pci_5"
INFO    | 	 argv[87] = "-device"
INFO    | 	 argv[88] = "virtio_input_multi_touch_pci_6"
INFO    | 	 argv[89] = "-device"
INFO    | 	 argv[90] = "virtio_input_multi_touch_pci_7"
INFO    | 	 argv[91] = "-device"
INFO    | 	 argv[92] = "virtio_input_multi_touch_pci_8"
INFO    | 	 argv[93] = "-device"
INFO    | 	 argv[94] = "virtio_input_multi_touch_pci_9"
INFO    | 	 argv[95] = "-device"
INFO    | 	 argv[96] = "virtio_input_multi_touch_pci_10"
INFO    | 	 argv[97] = "-device"
INFO    | 	 argv[98] = "virtio_input_multi_touch_pci_11"
INFO    | 	 argv[99] = "-device"
INFO    | 	 argv[100] = "virtio-keyboard-pci"
INFO    | 	 argv[101] = "-netdev"
INFO    | 	 argv[102] = "user,id=virtio-wifi,dhcpstart=10.0.2.16"
INFO    | 	 argv[103] = "-device"
INFO    | 	 argv[104] = "virtio-wifi-pci,netdev=virtio-wifi"
INFO    | 	 argv[105] = "-device"
INFO    | 	 argv[106] = "virtio-vsock-pci,guest-cid=77"
INFO    | 	 argv[107] = "-L"
INFO    | 	 argv[108] = "/data/app/android/Android/Sdk/emulator/lib/pc-bios"
INFO    | 	 argv[109] = "-soundhw"
INFO    | 	 argv[110] = "virtio-snd-pci"
INFO    | 	 argv[111] = "-vga"
INFO    | 	 argv[112] = "none"
INFO    | 	 argv[113] = "-append"
INFO    | 	 argv[114] = "no_timer_check 8250.nr_uarts=1 clocksource=pit console=ttyS0,38400 cma=326M@0-4G loop.max_part=7 ramoops.mem_address=0xff018000 ramoops.mem_size=0x10000 memmap=0x10000$0xff018000 printk.devkmsg=on bootconfig"
INFO    | 	 argv[115] = "-android-hw"
INFO    | 	 argv[116] = "/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/hardware-qemu.ini"
INFO    | Concatenated QEMU options: /data/app/android/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64 -dns-server 127.0.0.53 -mem-path /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/snapshots/default_boot/ram.img -mem-file-shared -serial stdio -device goldfish_pstore,addr=0xff018000,size=0x10000,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/data/misc/pstore/pstore.bin -cpu android64-xts -enable-kvm -smp cores=4 -m 3072 -lcd-density 560 -object iothread,id=disk-iothread -nodefaults -kernel /data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//kernel-ranchu -initrd /home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/initrd -drive if=none,index=0,id=system,if=none,file=/data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//system.img,read-only -device virtio-blk-pci,drive=system,iothread=disk-iothread,modern-pio-notify -drive if=none,index=1,id=cache,if=none,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/cache.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576 -device virtio-blk-pci,drive=cache,iothread=disk-iothread,modern-pio-notify -drive if=none,index=2,id=userdata,if=none,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/userdata-qemu.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576 -device virtio-blk-pci,drive=userdata,iothread=disk-iothread,modern-pio-notify -drive if=none,index=3,id=encrypt,if=none,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/encryptionkey.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576 -device virtio-blk-pci,drive=encrypt,iothread=disk-iothread,modern-pio-notify -drive if=none,index=4,id=vendor,if=none,file=/data/app/android/Android/Sdk/system-images/android-34/google_apis_playstore/x86_64//vendor.img,read-only -device virtio-blk-pci,drive=vendor,iothread=disk-iothread,modern-pio-notify -drive if=none,index=5,id=sdcard,if=none,file=/home/takeseem/.android/avd/../avd/Pixel_7_Pro_API_34.avd/sdcard.
DEBUG   | Android qemu version 34.1.10.0 (build_id 11042718) (CL:N/A)
DEBUG   | Starting QEMU main loop
DEBUG   | registered 'boot-properties' qemud service
DEBUG   | Adding boot property: 'ro.opengles.version' = '196608'
DEBUG   | Adding boot property: 'qemu.sf.fake_camera' = 'front'
DEBUG   | Adding boot property: 'qemu.adb.secure' = '1'
DEBUG   | Adding boot property: 'dalvik.vm.heapsize' = '576m'
DEBUG   | Adding boot property: 'qemu.hw.mainkeys' = '0'
DEBUG   | Adding boot property: 'qemu.sf.lcd_density' = '560'
DEBUG   | control console listening on port 5554, ADB on port 5555
DEBUG   | goldfish_events.have-dpad: false
DEBUG   | goldfish_events.have-trackball: false
DEBUG   | goldfish_events.have-camera: true
DEBUG   | goldfish_events.have-keyboard: false
DEBUG   | goldfish_events.have-lidswitch: false
DEBUG   | goldfish_events.have-tabletmode: false
DEBUG   | goldfish_events.have-touch: false
DEBUG   | goldfish_events.have-multitouch: false
DEBUG   | Adding boot property: 'net.wifi_mac_prefix' = '5554'
DEBUG   | Adding boot property: 'qemu.timezone' = 'Asia/Shanghai'
DEBUG   | android_hw_fingerprint_init: fingerprint qemud listen service initialized
WARNING | The emulator now requires a signed jwt token for gRPC access! Use the -grpc flag if you really want an open unprotected grpc port
DEBUG   | (input_volume_stats_reporter.cc:98): Will not log any `WebRTC.Audio.Apm.AppliedInputVolume.*` histogram stats.
DEBUG   | (input_volume_stats_reporter.cc:98): Will not log any `WebRTC.Audio.Apm.RecommendedInputVolume.*` histogram stats.
DEBUG   | (audio_processing_impl.cc:695): Injected APM submodules:
Echo control factory: 0
Echo detector: 0
Capture analyzer: 0
Capture post processor: 0
Render pre processor: 0
DEBUG   | (audio_processing_impl.cc:708): AudioProcessing: AudioProcessing::Config{ pipeline: { maximum_internal_processing_rate: 48000, multi_channel_render: 0, multi_channel_capture: 0 }, pre_amplifier: { enabled: 0, fixed_gain_factor: 1 },capture_level_adjustment: { enabled: 0, pre_gain_factor: 1, post_gain_factor: 1, analog_mic_gain_emulation: { enabled: 0, initial_level: 255 }}, high_pass_filter: { enabled: 0 }, echo_canceller: { enabled: 0, mobile_mode: 0, enforce_high_pass_filtering: 1 }, noise_suppression: { enabled: 0, level: Moderate }, transient_suppression: { enabled: 0 }, gain_controller1: { enabled: 0, mode: AdaptiveAnalog, target_level_dbfs: 3, compression_gain_db: 9, enable_limiter: 1, analog_gain_controller { enabled: 1, startup_min_volume: 0, clipped_level_min: 70, enable_digital_adaptive: 1, clipped_level_step: 15, clipped_ratio_threshold: 0.1, clipped_wait_frames: 300, clipping_predictor:  { enabled: 0, mode: 0, window_length: 5, reference_window_length: 5, reference_window_delay: 5, clipping_threshold: -1, crest_factor_margin: 3, use_predicted_step: 1 }}}, gain_controller2: { enabled: 0, fixed_digital: { gain_db: 0 }, adaptive_digital: { enabled: 0, headroom_db: 6, max_gain_db: 30, initial_gain_db: 8, max_gain_change_db_per_second: 3, max_output_noise_level_dbfs: -50 }, input_volume_control : { enabled 0}}
DEBUG   | (webrtc_voice_engine.cc:311): WebRtcVoiceEngine::WebRtcVoiceEngine
DEBUG   | (webrtc_voice_engine.cc:333): WebRtcVoiceEngine::Init
DEBUG   | (webrtc_voice_engine.cc:424): WebRtcVoiceEngine::ApplyOptions: AudioOptions {aec: 1, agc: 1, ns: 1, hf: 1, swap: 0, audio_jitter_buffer_max_packets: 200, audio_jitter_buffer_fast_accelerate: 0, audio_jitter_buffer_min_delay_ms: 0, }
DEBUG   | (audio_processing_impl.cc:911): AudioProcessing::ApplyConfig: AudioProcessing::Config{ pipeline: { maximum_internal_processing_rate: 48000, multi_channel_render: 0, multi_channel_capture: 0 }, pre_amplifier: { enabled: 0, fixed_gain_factor: 1 },capture_level_adjustment: { enabled: 0, pre_gain_factor: 1, post_gain_factor: 1, analog_mic_gain_emulation: { enabled: 0, initial_level: 255 }}, high_pass_filter: { enabled: 1 }, echo_canceller: { enabled: 1, mobile_mode: 0, enforce_high_pass_filtering: 1 }, noise_suppression: { enabled: 1, level: High }, transient_suppression: { enabled: 0 }, gain_controller1: { enabled: 1, mode: AdaptiveAnalog, target_level_dbfs: 3, compression_gain_db: 9, enable_limiter: 1, analog_gain_controller { enabled: 1, startup_min_volume: 0, clipped_level_min: 70, enable_digital_adaptive: 1, clipped_level_step: 15, clipped_ratio_threshold: 0.1, clipped_wait_frames: 300, clipping_predictor:  { enabled: 0, mode: 0, window_length: 5, reference_window_length: 5, reference_window_delay: 5, clipping_threshold: -1, crest_factor_margin: 3, use_predicted_step: 1 }}}, gain_controller2: { enabled: 0, fixed_digital: { gain_db: 0 }, adaptive_digital: { enabled: 0, headroom_db: 6, max_gain_db: 30, initial_gain_db: 8, max_gain_change_db_per_second: 3, max_output_noise_level_dbfs: -50 }, input_volume_control : { enabled 0}}
DEBUG   | (matched_filter.cc:139): AEC3: Pre echo configuration:  threshold = 0.5, mode =  0.
DEBUG   | (transparent_mode.cc:239): AEC3 Transparent Mode: Legacy
DEBUG   | (echo_canceller3.cc:793): AEC3 created with sample rate: 16000 Hz, num render channels: 1, num capture channels: 1
DEBUG   | (clipping_predictor.cc:358): [AGC2] Clipping prediction disabled.
DEBUG   | (agc_manager_direct.cc:481): [agc] analog controller enabled: yes
DEBUG   | (agc_manager_direct.cc:484): [agc] Min mic level: 12 (overridden: no)
DEBUG   | (input_volume_stats_reporter.cc:98): Will not log any `WebRTC.Audio.Apm.AppliedInputVolume.*` histogram stats.
DEBUG   | (input_volume_stats_reporter.cc:98): Will not log any `WebRTC.Audio.Apm.RecommendedInputVolume.*` histogram stats.
DEBUG   | (audio_processing_impl.cc:695): Injected APM submodules:
Echo control factory: 0
Echo detector: 0
Capture analyzer: 0
Capture post processor: 0
Render pre processor: 0
DEBUG   | (audio_processing_impl.cc:708): AudioProcessing: AudioProcessing::Config{ pipeline: { maximum_internal_processing_rate: 48000, multi_channel_render: 0, multi_channel_capture: 0 }, pre_amplifier: { enabled: 0, fixed_gain_factor: 1 },capture_level_adjustment: { enabled: 0, pre_gain_factor: 1, post_gain_factor: 1, analog_mic_gain_emulation: { enabled: 0, initial_level: 255 }}, high_pass_filter: { enabled: 0 }, echo_canceller: { enabled: 0, mobile_mode: 0, enforce_high_pass_filtering: 1 }, noise_suppression: { enabled: 0, level: Moderate }, transient_suppression: { enabled: 0 }, gain_controller1: { enabled: 0, mode: AdaptiveAnalog, target_level_dbfs: 3, compression_gain_db: 9, enable_limiter: 1, analog_gain_controller { enabled: 1, startup_min_volume: 0, clipped_level_min: 70, enable_digital_adaptive: 1, clipped_level_step: 15, clipped_ratio_threshold: 0.1, clipped_wait_frames: 300, clipping_predictor:  { enabled: 0, mode: 0, window_length: 5, reference_window_length: 5, reference_window_delay: 5, clipping_threshold: -1, crest_factor_margin: 3, use_predicted_step: 1 }}}, gain_controller2: { enabled: 0, fixed_digital: { gain_db: 0 }, adaptive_digital: { enabled: 0, headroom_db: 6, max_gain_db: 30, initial_gain_db: 8, max_gain_change_db_per_second: 3, max_output_noise_level_dbfs: -50 }, input_volume_control : { enabled 0}}
DEBUG   | (webrtc_voice_engine.cc:311): WebRtcVoiceEngine::WebRtcVoiceEngine
DEBUG   | (webrtc_voice_engine.cc:333): WebRtcVoiceEngine::Init
DEBUG   | (webrtc_voice_engine.cc:424): WebRtcVoiceEngine::ApplyOptions: AudioOptions {aec: 1, agc: 1, ns: 1, hf: 1, swap: 0, audio_jitter_buffer_max_packets: 200, audio_jitter_buffer_fast_accelerate: 0, audio_jitter_buffer_min_delay_ms: 0, }
DEBUG   | (audio_processing_impl.cc:911): AudioProcessing::ApplyConfig: AudioProcessing::Config{ pipeline: { maximum_internal_processing_rate: 48000, multi_channel_render: 0, multi_channel_capture: 0 }, pre_amplifier: { enabled: 0, fixed_gain_factor: 1 },capture_level_adjustment: { enabled: 0, pre_gain_factor: 1, post_gain_factor: 1, analog_mic_gain_emulation: { enabled: 0, initial_level: 255 }}, high_pass_filter: { enabled: 1 }, echo_canceller: { enabled: 1, mobile_mode: 0, enforce_high_pass_filtering: 1 }, noise_suppression: { enabled: 1, level: High }, transient_suppression: { enabled: 0 }, gain_controller1: { enabled: 1, mode: AdaptiveAnalog, target_level_dbfs: 3, compression_gain_db: 9, enable_limiter: 1, analog_gain_controller { enabled: 1, startup_min_volume: 0, clipped_level_min: 70, enable_digital_adaptive: 1, clipped_level_step: 15, clipped_ratio_threshold: 0.1, clipped_wait_frames: 300, clipping_predictor:  { enabled: 0, mode: 0, window_length: 5, reference_window_length: 5, reference_window_delay: 5, clipping_threshold: -1, crest_factor_margin: 3, use_predicted_step: 1 }}}, gain_controller2: { enabled: 0, fixed_digital: { gain_db: 0 }, adaptive_digital: { enabled: 0, headroom_db: 6, max_gain_db: 30, initial_gain_db: 8, max_gain_change_db_per_second: 3, max_output_noise_level_dbfs: -50 }, input_volume_control : { enabled 0}}
DEBUG   | (matched_filter.cc:139): AEC3: Pre echo configuration:  threshold = 0.5, mode =  0.
DEBUG   | (transparent_mode.cc:239): AEC3 Transparent Mode: Legacy
DEBUG   | (echo_canceller3.cc:793): AEC3 created with sample rate: 16000 Hz, num render channels: 1, num capture channels: 1
DEBUG   | (clipping_predictor.cc:358): [AGC2] Clipping prediction disabled.
DEBUG   | (agc_manager_direct.cc:481): [agc] analog controller enabled: yes
DEBUG   | (agc_manager_direct.cc:484): [agc] Min mic level: 12 (overridden: no)
INFO    | Using security allow list from: /data/app/android/Android/Sdk/emulator/lib/emulator_access.json
WARNING | *** Basic token auth should only be used by android-studio ***
INFO    | The active JSON Web Key Sets can be found here: /run/user/1000/avd/running/61527/jwks/c0f8ea9d-0d55-4cdd-9f5e-63734fecae6a/active.jwk
INFO    | Scanning /run/user/1000/avd/running/61527/jwks/c0f8ea9d-0d55-4cdd-9f5e-63734fecae6a for jwk keys.
INFO    | Started GRPC server at 127.0.0.1:8554, security: Local, auth: +token
INFO    | Advertising in: /run/user/1000/avd/running/pid_61527.ini
DEBUG   | Successfully initialized Wi-Fi
DEBUG   | emulator_window_fb_rotate
I1203 23:52:09.429387   61588 FrameBuffer.cpp:3682] setDisplayConfigs w 1440 h 3120 dpiX 560 dpiY 560
DEBUG   | setDisplayPose 0 x 0 y 0 w 1440 h 3120 dpi 0
I1203 23:52:09.429435   61588 FrameBuffer.cpp:3695] setDisplayActiveConfig 0
DEBUG   |  no root specified: 
DEBUG   | Path:/data/app/android/Android/Sdk/platform-tools/adb protocol version: 41
DEBUG   | Found: 1 adb executables
DEBUG   | Adb: /data/app/android/Android/Sdk/platform-tools/adb
DEBUG   | Path:/data/app/android/Android/Sdk/platform-tools/adb protocol version: 41
DEBUG   | config multidisplay with config.ini 0x0 0x0 0x0
DEBUG   | No acpi ini file provided, using default
DEBUG   | added one RIL client
INFO    | Loading snapshot 'default_boot'...
DEBUG   | OpenGL Vendor=[Google (AMD)]
DEBUG   | OpenGL Renderer=[Android Emulator OpenGL ES Translator (GFX1103_R1 (gfx1103_r1, LLVM 15.0.7, DRM 3.49, 6.2.0-37-generic))]
DEBUG   | OpenGL Version=[OpenGL ES 3.0 (4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1)]
WARNING | Device 'cache' does not have the requested snapshot 'default_boot'
WARNING | Failed to load snapshot 'default_boot'
DEBUG   | No acpi ini file provided, using default

DEBUG   | getMultiDisplay 0 x -1 y -1 w 1440 h 3120 dpi 560 flag 0 enable 1
DEBUG   | getMultiDisplay 0 x -1 y -1 w 1440 h 3120 dpi 560 flag 0 enable 1 (3x)
DEBUG   | change window size to 1440x3120
[  134.156841] servicemanager: Could not find android.hardware.graphics.allocator.IAllocator/default in the VINTF manifest.
I1203 23:54:24.937362   61797 VkDecoderGlobalState.cpp:1551] gfxstream_texture_format_manifest: VK_FORMAT_R8G8B8A8_UNORM
error: kvm run failed Bad address
RAX=0000704545376000 RBX=000070454548f400 RCX=0000000000000000 RDX=0000000000119400
RSI=0000000008446000 RDI=0000704545376000 RBP=0000704545376000 RSP=00007045531ddee0
R8 =0000704545377000 R9 =0000000000000010 R10=000038fa0012b800 R11=00000000000cc000
R12=0000000000119400 R13=0000000000001680 R14=0000000000000000 R15=0000000000000000
RIP=00007048574e1ac4 RFL=00000206 [-----P-] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =0000 0000000000000000 00000000 00000000
CS =0033 0000000000000000 ffffffff 00a0fb00 DPL=3 CS64 [-RA]
SS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
DS =0000 0000000000000000 00000000 00000000
FS =0000 00007045531e2000 00000000 00000000
GS =0000 00007045c352b950 00000000 00000000
LDT=0000 0000000000000000 00000000 00000000
TR =0040 fffffe0000079000 00004087 00008b00 DPL=0 TSS64-busy
GDT=     fffffe0000077000 0000007f
IDT=     fffffe0000000000 00000fff
CR0=80050033 CR2=000070454d7bc000 CR3=00000000b6954000 CR4=000406a0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=41 0f 6f 4c 30 10 f3 41 0f 6f 54 30 20 f3 41 0f 6f 5c 30 30 <66> 41 0f 7f 00 41 0f 29 48 10 41 0f 29 50 20 41 0f 29 58 30 4d 8d 40 40 4c 39 c3 77 bf 48

Message last modified on Dec 3, 2023 03:55PM

ta...@gmail.com <ta...@gmail.com> #138Dec 3, 2023 04:10PM

settings -> Advanced, OpenGL ES renderer: SwiftShader ==> open chrome running ok

./Sdk/emulator/emulator -avd Pixel_7_Pro_API_34 -verbose -show-kernel open chrome console print

[   52.647636] servicemanager: Could not find android.hardware.graphics.allocator.IAllocator/default in the VINTF manifest.
I1204 00:09:11.066272   64426 VkDecoderGlobalState.cpp:444] Creating Vulkan instance for app: Chromium
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
I1204 00:09:11.100449   64426 VkDecoderGlobalState.cpp:1271] Created new VkDevice. ASTC emulation? 0. CPU decoding? 0
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000338000
../../third_party/SwiftShader/src/Vulkan/VkPhysicalDevice.cpp:649 WARNING: UNSUPPORTED: curExtension->sType: 1000437000
[   53.816821] servicemanager: Could not find android.hardware.graphics.allocator.IAllocator/default in the VINTF manifest.
I1204 00:09:11.334916   64428 VkDecoderGlobalState.cpp:1551] gfxstream_texture_format_manifest: VK_FORMAT_R8G8B8A8_UNORM
I1204 00:09:11.474187   64426 VkDecoderGlobalState.cpp:1551] gfxstream_texture_format_manifest: VK_FORMAT_R8_UNORM
[   54.653653] servicemanager: Since 'artd' could not be found, trying to start it as a lazy AIDL service. (if it's not configured to be a lazy service, it may be stuck starting or still starting).
[   54.656529] init: starting service 'artd'...
[   54.681796] init: ... started service 'artd' has pid 4566
[   54.683066] init: Control message: Processed ctl.interface_start for 'aidl/artd' from pid: 156 (/system/bin/servicemanager)
[   54.694136] BpBinder: onLastStrongRef automatically unlinking death recipients: 
[   54.704357] servicemanager: Notifying artd they do (previously: don't) have clients when service is guaranteed to be in use
[   58.584202] servicemanager: Found android.hardware.security.keymint.IRemotelyProvisionedComponent/default in device VINTF manifest.

settings -> Advanced, OpenGL ES renderer: Desktop native OpenGL ==> AVD crash when open chrome

I1204 00:13:03.050591   64903 VkDecoderGlobalState.cpp:1551] gfxstream_texture_format_manifest: VK_FORMAT_R8G8B8A8_UNORM
error: kvm run failed Bad address
RAX=00007bc5de263000 RBX=00007bc5de37c400 RCX=0000000000000000 RDX=0000000000119400
RSI=0000000000a6a000 RDI=00007bc5de263000 RBP=00007bc5de263000 RSP=00007bc5e2dddee0
R8 =00007bc5de264000 R9 =0000000000000010 R10=00003de80012b800 R11=0000000000000047
R12=0000000000119400 R13=0000000000001680 R14=0000000000000000 R15=0000000000000000
RIP=00007bc8f6c87ac4 RFL=00000206 [-----P-] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =0000 0000000000000000 00000000 00000000
CS =0033 0000000000000000 ffffffff 00a0fb00 DPL=3 CS64 [-RA]
SS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
DS =0000 0000000000000000 00000000 00000000
FS =0000 00007bc5e2de2000 00000000 00000000
GS =0000 00007bc80d48f520 00000000 00000000
LDT=0000 0000000000000000 00000000 00000000
TR =0040 fffffe0000003000 00004087 00008b00 DPL=0 TSS64-busy
GDT=     fffffe0000001000 0000007f
IDT=     fffffe0000000000 00000fff
CR0=80050033 CR2=00007bc5deccd000 CR3=0000000045db0000 CR4=000406b0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=41 0f 6f 4c 30 10 f3 41 0f 6f 54 30 20 f3 41 0f 6f 5c 30 30 <66> 41 0f 7f 00 41 0f 29 48 10 41 0f 29 50 20 41 0f 29 58 30 4d 8d 40 40 4c 39 c3 77 bf 48
DEBUG   | Timed out with running command

Message last modified on Dec 3, 2023 04:15PM

ta...@gmail.com <ta...@gmail.com> #139Dec 3, 2023 04:35PM

settings -> Advanced, OpenGL ES renderer: Autodetect based on host(default), OpenGL ES API level: Autoselect

my solution

for Android Studio start AVD

echo "Vulkan = off" >> ~/.android/advancedFeatures.ini

direct start AVD with cmd: emulator

./Sdk/emulator/emulator -avd $your_avd_name -verbose -show-kernel -feature -Vulka

why AVD hang when open chrome?

chrome use Vulkan from API 30

Starting with API level 30, Chrome uses the Vulkan graphics library as its rendering backend, and it could have compatibility issues on certain machines. If Chrome does not render correctly for you, try to launch the emulator from the command line with the flag -feature -Vulkan

my test details

-verbose -show-kernel -feature -Vulkan <-- AVD don't crash, chrome running ok
-verbose -show-kernel -feature -GLDirectMem <-- AVD don't crash, chrome not crash but page is blank. console print:

DEBUG   | getMultiDisplay 0 x -1 y -1 w 1440 h 3120 dpi 560 flag 0 enable 1 (3x)
DEBUG   | change window size to 1440x3120
[  120.657520] servicemanager: Could not find android.hardware.graphics.allocator.IAllocator/default in the VINTF manifest.
I1204 00:23:17.207660   65957 VkDecoderGlobalState.cpp:1551] gfxstream_texture_format_manifest: VK_FORMAT_R8G8B8A8_UNORM
[  121.050977] servicemanager: Could not find android.hardware.graphics.allocator.IAllocator/default in the VINTF manifest.
I1204 00:23:17.372141   65957 VkDecoderGlobalState.cpp:1551] gfxstream_texture_format_manifest: VK_FORMAT_R8_UNORM
DEBUG   | getMultiDisplay 0 x 0 y 0 w 1440 h 3120 dpi 560 flag 0 enable 1
[  127.305413] servicemanager: Could not find android.hardware.graphics.allocator.IAllocator/default in the VINTF manifest.
[  134.296904] binder: undelivered transaction 156259, process died.
[  134.298405] binder: undelivered transaction 156260, process died.
[  134.299351] binder: undelivered transaction 156258, process died.

-verbose -show-kernel -feature -GLDirectMem -feature -GLDMA <-- it's the same -verbose -show-kernel -feature -GLDirectMem
-verbose -show-kernel -feature -GLDirectMem -feature -GLDMA -feature -GLDMA2 <-- it's the same -verbose -show-kernel -feature -GLDirectMem
-verbose -show-kernel -feature -GLDirectMem -feature -GLDMA2 <-- AVD don't crash, chrome not crash but splash screen. console print:

[  145.147145] servicemanager: Could not find android.hardware.graphics.allocator.IAllocator/default in the VINTF manifest.
I1204 00:31:23.907154   67481 VkDecoderGlobalState.cpp:444] Creating Vulkan instance for app: Chromium
I1204 00:31:23.930584   67481 VkDecoderGlobalState.cpp:1271] Created new VkDevice. ASTC emulation? 1. CPU decoding? 0
I1204 00:31:24.007138   67481 VkDecoderGlobalState.cpp:1551] gfxstream_texture_format_manifest: VK_FORMAT_R8G8B8A8_UNORM
[  145.606239] servicemanager: Could not find android.hardware.graphics.allocator.IAllocator/default in the VINTF manifest.
I1204 00:31:24.090714   67481 VkDecoderGlobalState.cpp:1551] gfxstream_texture_format_manifest: VK_FORMAT_R8_UNORM

-verbose -show-kernel -feature -GLDirectMem -feature -GLDMA2 -feature -Vulkan <-- AVD is ok, chrome is ok, and can load state when restart AVD

Message last modified on Dec 3, 2023 05:55PM

ya...@google.com <ya...@google.com> #140Jan 10, 2024 07:45PM

More patches coming up in emulator stable 33.1.24 and next canary 34.2.3. Carlos, if this issue does not repro on 34.2.3, we might be able to close this bug.

aa...@xqz.ca <aa...@xqz.ca> #141Jan 12, 2024 04:22PM

I thought this was resolved but it actually seems not to be for me.

Message last modified on Jan 12, 2024 04:33PM

ya...@google.com <ya...@google.com> #142Jan 12, 2024 07:32PM

Hi,

Because many different kinds of issues are involved in this bug, it would be great if you could tell us which emulator version + system image version you are using, your OS, your graphics card model, as well as a short description of what happens (emulator crashes when loading a webpage, emulator does not crash but webpage looks empty, webpage flickers, etc).

Thanks!

ca...@google.com <ca...@google.com> #143Jan 16, 2024 09:29PM

Chrome is running fine on a Windows machine with:

nVidia P1000. Driver 535.98
nVidia RTX 3060. Driver 546.33
AMD RDNA 3 Integrated graphics. Driver 31.0.22024.3002

A setup that was having issues is the one with an 2080 Super as we discussed on b/318921299 . Where even on 34.2.3, it was not displaying the websites correctly and it would lock up the entire computer on exit.

Otherwise all the other setups were running and exiting chrome no problem. Even when using swiftshader.

Emulator: 34.2.3-11271302
System Image build: [ro.vendor_dlkm.build.fingerprint]: [google/sdk_gphone64_x86_64/emu64xa:14/UE1A.230829.036/11036701:user/release-keys]

swiftshader.mov

13 MB

Download

Hardware.mov

25 MB

Download

ca...@google.com <ca...@google.com> #144Jan 17, 2024 07:38PM

Got this to repro on a Steam Deck with RDNA 2.0 Van Gogh gpu and on emu 34.2.4.0-11307001

The verbose output looks similar to comment #1

DEBUG   | MultiDisplayPipe created 0x5597d86fa540
DEBUG   | MultiDisplayPipe recevied QUERY
DEBUG   | MultiDisplayPipe send add id 0 width 2208 height 1840 dpi 420 flag 0
I0117 11:26:42.953790    7567 VkDecoderGlobalState.cpp:444] Creating Vulkan instance for app: Chromium
I0117 11:26:43.475909    7567 VkDecoderGlobalState.cpp:1279] Created new VkDevice. ASTC emulation? 1. CPU decoding? 0
DEBUG   | getMultiDisplay 0 x -1 y -1 w 2208 h 1840 dpi 420 flag 0 enable 1
DEBUG   | getMultiDisplay 0 x -1 y -1 w 2208 h 1840 dpi 420 flag 0 enable 1 (21x)
DEBUG   | getMultiDisplay 0 x 0 y 0 w 2208 h 1840 dpi 420 flag 0 enable 1
I0117 11:27:17.780623    7567 VkDecoderGlobalState.cpp:1559] gfxstream_texture_format_manifest: VK_FORMAT_R8G8B8A8_UNORM
error: kvm run failed Bad address
RAX=000079915f050000 RBX=000079915f8ae000 RCX=0000000000000000 RDX=0000000000225d80
RSI=000000000085e000 RDI=000079915f050000 RBP=000079915f050000 RSP=00007991623ddee0
R8 =000079915f050040 R9 =0000000000000010 R10=00001e1c0012b800 R11=0000000000000045
R12=0000000000225d80 R13=0000000000002280 R14=0000000000000000 R15=0000000000000000
RIP=000079947ce91a4e RFL=00000206 [-----P-] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =0000 0000000000000000 00000000 00000000
CS =0033 0000000000000000 ffffffff 00a0fb00 DPL=3 CS64 [-RA]
SS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
DS =0000 0000000000000000 00000000 00000000
FS =0000 00007991623e2000 00000000 00000000
GS =0000 000079935eabccc0 00000000 00000000
LDT=0000 fffffe0000000000 00000000 00000000
TR =0040 fffffe0000003000 00004087 00008b00 DPL=0 TSS64-busy
GDT=     fffffe0000001000 0000007f
IDT=     fffffe0000000000 00000fff
CR0=80050033 CR2=000079915f8ae000 CR3=0000000003792000 CR4=000406b0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=41 0f 6f 6c 30 10 f3 41 0f 6f 74 30 20 f3 41 0f 6f 7c 30 30 <f3> 0f 7f 07 f3 0f 7f 4f 10 f3 0f 7f 57 20 f3 0f 7f 5f 30 66 41 0f 7f 20 41 0f 29 68 10 41
DEBUG   | getMultiDisplay 0 x 0 y 0 w 2208 h 1840 dpi 420 flag 0 enable 1 (119x)
DEBUG   | Timed out with running command 
^CDEBUG   | Timed out with running command  (14x)
INFO    | Wait for emulator (pid 7066) 20 seconds to shutdown gracefully before kill;you can set environment variable ANDROID_EMULATOR_WAIT_TIME_BEFORE_KILL(in seconds) to change the default value (20 seconds)
INFO    | Wait for emulator (pid 7066) 20 seconds to shutdown gracefully before kill;you can set environment variable ANDROID_EMULATOR_WAIT_TIME_BEFORE_KILL(in seconds) to change the default value (20 seconds)

WARNING | Not saving state: current state does not support snapshotting
INFO    | Deleting snapshot default_boot
INFO    | Deleting snapshot default_boot
ERROR   | stop: Not implemented
DEBUG   | Done with QEMU main loop
Segmentation fault (core dumped)
(139)(deck@steamdeck emulator)$

verbose.txt

39 KB

View

Download

logcat.txt

1024 KB

View

Download

2024-01-17 11-26-57.mp4

4.3 MB

Download

ya...@google.com <ya...@google.com> #145Jan 17, 2024 11:17PM

Carlos do you have the crash report id?

ca...@google.com <ca...@google.com> #146Jan 17, 2024 11:48PM

It does not crash but stays frozen. After launching again from a force close it doesn't produce a crash report.

ta...@gmail.com <ta...@gmail.com> #147Jan 18, 2024 05:16PM

Thank you. It's better, now it's not crash, but stay frozen.

.android/advancedFeatures.ini #Vulkan = off it is frozen in canary 34.2.3

I must to keep disable Vulkan .android/advancedFeatures.ini Vulkan = off to keep chrome running ok.

Message last modified on Jan 22, 2024 05:56AM

ya...@google.com <ya...@google.com> Feb 5, 2024 06:44PM

Reassigned to ko...@google.com.

ko...@google.com <ko...@google.com> Feb 13, 2024 03:42PM

Accepted by ko...@google.com.

bo...@google.com <bo...@google.com> #148Feb 22, 2024 05:25PM

This bug is common for amd gpu, where it has problem working with kvm,

we recently had a work around for that problem and you can try

https://ci.android.com/builds/submitted/11484481/emulator-linux_x64_gfxstream/latest

https://ci.android.com/builds/submitted/11484481/emulator-linux_x64_gfxstream/latest/sdk-repo-linux-emulator-11484481.zip

we will have a canary emulator with that fix coming out soon, if you want to wait

Message last modified on Feb 22, 2024 05:29PM

bo...@google.com <bo...@google.com> #149Feb 22, 2024 05:28PM

note, the fix in #148 is for linux on amd gpu;

for windows crash, it might be something else.

ro...@veeva.com <ro...@veeva.com> #150Feb 23, 2024 08:33AM

#148 I just tried with sdk-repo-linux-emulator-11484481.zip and for me it still freezes as soon as I open a website (e.g. I do a Google search).

Attached the output of emulator -avd Nexus_5_API_30_Play -verbose -show-kernel &> emu.log

Message last modified on Feb 23, 2024 08:34AM

emu.log

174 KB

View

Download

bo...@google.com <bo...@google.com> #151Feb 23, 2024 02:34PM

you have intel gpu: Intel(R) Graphics (RPL-P)

you can add option to #150
-feature VulkanAllocateDeviceMemoryOnly

and post the output here please

le...@gmail.com <le...@gmail.com> #152Feb 23, 2024 02:43PM

you have intel gpu: Intel(R) Graphics (RPL-P)

Sorry, I forgot to mention that.

Attached the output of emulator -avd Nexus_5_API_30_Play -verbose -show-kernel -feature VulkanAllocateDeviceMemoryOnly &> emu.log

emu.log

169 KB

View

Download

bo...@google.com <bo...@google.com> #153Feb 23, 2024 03:22PM

have you tried api 34 ?

le...@gmail.com <le...@gmail.com> #154Feb 23, 2024 03:26PM

I just tried and it freezes as soon as I open Chrome. Log attached.

emu.log

243 KB

View

Download

bo...@google.com <bo...@google.com> #155Feb 23, 2024 03:33PM

Thanks for the update,

if you can, please try this

https://sdk.lunarg.com/sdk/download/1.3.275.0/linux/vulkansdk-linux-x86_64-1.3.275.0.tar.xz

run the x86_64/bin/vulkaninfo and upload the information there so I can have better idea of
the vulkan support your intel gpu has.

the build in #148 is for the issue we found on AMD gpu, it does not seem to fix intel gpu for the moment
and.I hope to get more details about your intel gpu so to find one that can reproduce. thanks

le...@gmail.com <le...@gmail.com> #156Feb 23, 2024 03:44PM

Sure, here you go. Let me know if I can help with some other tests.

vulkaninfo.txt

107 KB

View

Download

bo...@google.com <bo...@google.com> #157Feb 23, 2024 04:44PM

Thanks,

I have Intel Graphics ADL GT2, and it runs ok with vulkan, not perfect as I saw some blackscreen when rendering chrome, but
it does not freeze

my driver is 23.3.3 vs your driver is 24.0.1, updating my driver and try again

still cannot reproduce

I am running on ubuntu 24.04 btw

Message last modified on Feb 23, 2024 04:47PM

bo...@google.com <bo...@google.com> #158Feb 23, 2024 04:54PM

if you can, please try open the
(after
source setup-env.sh under vunkan dir)

x86_64/bin/vkconfig
(you might need to install a bunch of libxcb* libraries, sudo apt install libxcb*)

and click the "Validation" radio checkbox,

then source setup-env.sh under vunkan dir again, and launch emulator
it should catch some validation problem and please post it.

bo...@google.com <bo...@google.com> #159Feb 23, 2024 05:32PM

This might help but please try this option as well
-feature SystemBlob

le...@gmail.com <le...@gmail.com> #160Feb 23, 2024 07:51PM

So I did some tests and it seems that using -feature SystemBlob fixes the issue (or at least it did not crash the 3 times I tried it). Is there a way to add this SystemBlob to the advancedFeatures.ini file so that it will be executed automatically every time the emulator runs?

BTW, I tried also to follow the instructions for the x86_64/bin/vkconfig, not sure if I did it right but I've attached the logs using SystemBlob and without (where it crashed).

Message last modified on Feb 23, 2024 07:53PM

WithoutSystemBlob.txt

186 KB

View

Download

SystemBlob.txt

196 KB

View

Download

Screenshot from 2024-02-23 20-48-10.png

319 KB

View

Download

ya...@google.com <ya...@google.com> #161Feb 26, 2024 12:33AM

When will the fix land on the goldfish instances? All UI tests that open up the browser are blocked by this. Thanks!

ko...@google.com <ko...@google.com> #162Feb 26, 2024 03:51PM

Yang, the workaround for AMD GPU issue is submitted, but we're still working on a fix for the Intel related problems. Can you provide a link to the failing UI tests so that I can check if it's the same issue?

bo...@google.com <bo...@google.com> #163Feb 26, 2024 07:23PM

Serdar,
with SystemBlob turned on for Intel GPU, the "Bad Address" does not show up anymore (so far);
however, it seems there are some blackscreens in chrome once you open any of the tabs (such as youtube).
not sure what else went wrong.

bo...@google.com <bo...@google.com> #164Feb 26, 2024 07:26PM

maybe some extensions are not turned on for Intel GPU ?

on amd gpu, systemblob (after some hack to just use anonymous mmap in sharedmanager) does show normal rendering of chrome ;

Message last modified on Feb 26, 2024 07:26PM

bo...@google.com <bo...@google.com> #165Feb 26, 2024 09:42PM

I tried a couple of time on my intel gpu, and the "Bad Address" happens occasionally,

it appears that there is some race condition somewhere.

bo...@google.com <bo...@google.com> #166Feb 27, 2024 02:49PM

re #160,
thanks for the report, for the moment, we will enable "SystemBlob" on intel gpu when vulkan is turned on.
you can try this build that is from presubmit server with this cl:

https://android-review.git.corp.google.com/c/platform/external/qemu/+/2978634

sdk-repo-linux-emulator-P70651895.zip

245 MB

Download

bo...@google.com <bo...@google.com> #167Feb 27, 2024 02:57PM

btw, intel gpu has this blackscreen problem, regardless of whether SystembBlob is used

Screenshot_1709045746.png

35 KB

View

Download

le...@gmail.com <le...@gmail.com> #168Feb 27, 2024 03:01PM

Yeah I'm experiencing the black screen issue.

If I start the emulator from command line, with emulator -avd Nexus_5_API_34_Play -verbose -show-kernel, I get the black screen issue but it doesn't seem to freeze (I can close chrome or change tab). If I start it from AS it freezes as soon as the black screen is shown.

bo...@google.com <bo...@google.com> #169Feb 27, 2024 03:12PM

Thanks re #168

could you upload the idea.log when launch from AS ?

if it is due to kvm error of bad address, the idea.log should show that; and you can try adb shell to check whether it is the ANR (which will recover and adb shell should still work) or guest freezes completely

le...@gmail.com <le...@gmail.com> #170Feb 27, 2024 03:19PM

Sure, idea.log attached. The emulator freezes completely: notification and status bar are unresponsive and adb logcat and adb shell} do nothing.

idea.log

1.8 MB

View

Download

bo...@google.com <bo...@google.com> #171Feb 27, 2024 03:23PM

The stdio is still using the 34.1.17, which has the bug

22055918] INFO - Emulator: Nexus 5 API 29 Play - Process finished with exit code 0
2024-02-27 16:14:21,228 [22056050] INFO - #com.android.tools.idea.adb.AdbService - Device [emulator-5554] is offline
2024-02-27 16:14:26,206 [22061028] INFO - Emulator: Nexus 5 API 34 Play - /home/rleinardi/android-sdk/emulator-old/emulator -netdelay none -netspeed full -avd Nexus_5_API_34_Play -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
2024-02-27 16:14:26,214 [22061036] INFO - Emulator: Nexus 5 API 34 Play - Storing crashdata in: /tmp/android-rleinardi/emu-crash-34.1.17.db, detection is enabled for process: 1580157
2024-02-27 16:14:26,214 [22061036] INFO - Emulator: Nexus 5 API 34 Play - Android emulator version 34.1.17.0 (build_id 11438439) (CL:N/A)
2024-02-27 16:14:26,214 [22061036] INFO - Emulator: Nexus 5 API 34 Play - Found systemPath /home/rleinardi/android-sdk/system-images/android-34/google_apis_playstore/x86_64/
2024-02-27 16:14:26,425 [22061247] INFO - Emulator: Nexus 5 API 34 Play - Storing crashdata in: /tmp/android-rleinardi/emu-crash-34.1.17.db, detection is enabled for process: 1580157
2024-02-27 16:14:26,425 [22061247] INFO - Emulator: Nexus 5 API 34 Play - Duplicate loglines will be removed, if you wish to see each individual line launch with the -log-nofilter flag.
2024-02-27 16:14:26,425 [22061247] INFO - Emulator: Nexus 5 API 34 Play - Increasing RAM size to 2048MB
2024-02-27 16:14:26,425 [22061247] INFO - Emulator: Nexus 5 API 34 Play - library_mode host gpu mode host
2024-02-27 16:14:26,426 [22061248] INFO - Emulator: Nexus 5 API 34 Play - Initializing hardware OpenGLES emulation supportandroid_startOpenglesRenderer: gpu infoI0227 16:14:26.426136 1580157 HealthMonitor.cpp:279] HealthMonitor disabled.
2024-02-27 16:14:26,426 [22061248] INFO - Emulator: Nexus 5 API 34 Play - added library libvulkan.so
2024-02-27 16:14:26,458 [22061280] INFO - Emulator: Nexus 5 API 34 Play - createGlobalVkEmulation:964 Selecting Vulkan device: Intel(R) Graphics (RPL-P)
2024-02-27 16:14:26,460 [22061282] INFO - Emulator: Nexus 5 API 34 Play - initialize: Supports id properties, got a vulkan device UUID
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530414 1580157 VkCommonOperations.cpp:1226] Initializing VkEmulation features:
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530427 1580157 VkCommonOperations.cpp:1227] glInteropSupported: true
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530429 1580157 VkCommonOperations.cpp:1228] useDeferredCommands: true
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530430 1580157 VkCommonOperations.cpp:1230] createResourceWithRequirements: true
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530430 1580157 VkCommonOperations.cpp:1231] useVulkanComposition: false
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530431 1580157 VkCommonOperations.cpp:1232] useVulkanNativeSwapchain: false
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530432 1580157 VkCommonOperations.cpp:1233] enable guestRenderDoc: false
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530433 1580157 VkCommonOperations.cpp:1234] ASTC LDR emulation mode: 2
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530433 1580157 VkCommonOperations.cpp:1235] enable ETC2 emulation: true
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530434 1580157 VkCommonOperations.cpp:1236] enable Ycbcr emulation: false
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530434 1580157 VkCommonOperations.cpp:1237] guestUsesAngle: false
2024-02-27 16:14:26,530 [22061352] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530435 1580157 VkCommonOperations.cpp:1238] useDedicatedAllocations: true
2024-02-27 16:14:26,531 [22061353] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530956 1580157 FrameBuffer.cpp:486] Graphics Adapter Vendor Google (Intel)
2024-02-27 16:14:26,531 [22061353] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530958 1580157 FrameBuffer.cpp:487] Graphics Adapter Android Emulator OpenGL ES Translator (Mesa Intel(R) Graphics (RPL-P))
2024-02-27 16:14:26,531 [22061353] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530959 1580157 FrameBuffer.cpp:488] Graphics API Version OpenGL ES 3.0 (4.6 (Core Profile) Mesa 24.0.0 - kisak-mesa PPA)
2024-02-27 16:14:26,531 [22061353] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530960 1580157 FrameBuffer.cpp:489] Graphics API Extensions GL_OES_EGL_sync GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_depth24 GL_OES_depth32 GL_OES_element_index_uint GL_OES_texture_float GL_OES_texture_float_linear GL_OES_compressed_paletted_texture GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_packed_depth_stencil GL_OES_vertex_half_float GL_OES_texture_npot GL_OES_rgb8_rgba8 GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_shader_framebuffer_fetch GL_EXT_texture_format_BGRA8888 GL_APPLE_texture_format_BGRA8888
2024-02-27 16:14:26,531 [22061353] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.530967 1580157 FrameBuffer.cpp:490] Graphics Device Extensions N/A
2024-02-27 16:14:26,536 [22061358] INFO - Emulator: Nexus 5 API 34 Play - OpenGL Vendor=[Google (Intel)]OpenGL Renderer=[Android Emulator OpenGL ES Translator (Mesa Intel(R) Graphics (RPL-P))]OpenGL Version=[OpenGL ES 3.0 (4.6 (Core Profile) Mesa 24.0.0 - kisak-mesa PPA)]INFO | Sending adb public key [QAAAAE8/AkdRiNhUjTrfG15p3ir4LBMCkzp6+OxWeEtTk/ZFqlB9xtpuvQAkVO/2hORKr4L1HmyrUWD4YYrK9NUkhJzDug4vmJcEKKUKcaVsOSWvqfunNH1aW/mwQtQH1VSkZke9Rd9y73qBJpCnAjwv35ZerKRms9F+3oER9Ezv9xNnIxXBuzcCVOkb93Yh/ATx+8BH5Fkba86gYUp3YIUdGCgUuvuAIjwJNOR4mlSm3i4J9+9bHn51P1eCfznNjUgrjfkdumxXlbIvxldwX5JwIfE0ZUAX3lJrV3w1EtTHNs+b83a5hvoC2ZKIDKxy7bPXXcCzieGrqtWhOPHPhm0QovicT3LxmvSvX0uo3tMTw15s+NmfIeDhJa7BOE673biAC6yuF04yItgYhOPof61yZ/9nGCyE5OD47IH41CF3GG4meVDr4aZ/u8COaPRMpnQL3txV/B8qLpM75BtfaS0nV41kHq8bB/pss+7+Mi23KT/oL2mi6IUpObPaQbml9HkglDsSpGFVkztqSoJmEo6+WqoMuApN4zuM4NzB+mmy7FrI99mcZDcOQcny2T70BnCULHi9HRlOBGdBYCebXfdD8n9VSzeyITxvWDhw0XRGw0xPamwGGH6pGqcZNjYCQgGFIzfXr2ec/ZE2exS9fWHOGMZcpLbEaxnAl083+KRXL6wAqx5FNAEAAQA= rleinardi@unknown]
2024-02-27 16:14:26,624 [22061446] INFO - Emulator: Nexus 5 API 34 Play - Using security allow list from: /home/rleinardi/android-sdk/emulator-old/lib/emulator_access.json
2024-02-27 16:14:26,626 [22061448] WARN - Emulator: Nexus 5 API 34 Play - *** Basic token auth should only be used by android-studio ***
2024-02-27 16:14:26,627 [22061449] INFO - Emulator: Nexus 5 API 34 Play - The active JSON Web Key Sets can be found here: /run/user/1000/avd/running/1580157/jwks/c1f6a0ee-4979-4141-a124-8c1ec1f06be8/active.jwk
2024-02-27 16:14:26,627 [22061449] INFO - Emulator: Nexus 5 API 34 Play - Scanning /run/user/1000/avd/running/1580157/jwks/c1f6a0ee-4979-4141-a124-8c1ec1f06be8 for jwk keys.
2024-02-27 16:14:26,629 [22061451] INFO - Emulator: Nexus 5 API 34 Play - Started GRPC server at

127.0.0.1:8554, security: Local, auth: +token
2024-02-27 16:14:26,631 [22061453] INFO - Emulator: Nexus 5 API 34 Play - Advertising in: /run/user/1000/avd/running/pid_1580157.ini
2024-02-27 16:14:26,653 [22061475] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.653479 1580232 FrameBuffer.cpp:3707] setDisplayConfigs w 1080 h 1920 dpiX 480 dpiY 480
2024-02-27 16:14:26,653 [22061475] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:26.653496 1580232 FrameBuffer.cpp:3720] setDisplayActiveConfig 0
2024-02-27 16:14:26,721 [22061543] INFO - Emulator: Nexus 5 API 34 Play - Loading snapshot 'default_boot'...
2024-02-27 16:14:26,725 [22061547] WARN - Emulator: Nexus 5 API 34 Play - Device 'cache' does not have the requested snapshot 'default_boot'
2024-02-27 16:14:26,725 [22061547] WARN - Emulator: Nexus 5 API 34 Play - Failed to load snapshot 'default_boot'
2024-02-27 16:14:27,263 [22062085] INFO - Emulator: Nexus 5 API 34 Play - OpenGL Vendor=[Google (Intel)]OpenGL Renderer=[Android Emulator OpenGL ES Translator (Mesa Intel(R) Graphics (RPL-P))]OpenGL Version=[OpenGL ES 3.0 (4.6 (Core Profile) Mesa 24.0.0 - kisak-mesa PPA)]INFO | Camera notification event: cameraNotification { }
2024-02-27 16:14:27,263 [22062085] INFO - Emulator: Nexus 5 API 34 Play - Not yet booted
2024-02-27 16:14:27,263 [22062085] INFO - #com.android.tools.idea.streaming.emulator.EmulatorView - Received notification: cameraNotification { }
2024-02-27 16:14:27,688 [22062510] INFO - Emulator: Nexus 5 API 34 Play - Activated packet streamer for bluetooth emulation
2024-02-27 16:14:31,709 [22066531] INFO - Emulator: Nexus 5 API 34 Play - Not yet booted
2024-02-27 16:14:34,189 [22069011] INFO - Emulator: Nexus 5 API 34 Play - Displaychange event: 0
2024-02-27 16:14:34,189 [22069011] INFO - Emulator: Nexus 5 API 34 Play - Display notification event: event: DISPLAY_CONFIGURATIONS_CHANGED_UI displayConfigurationsChangedNotification { displayConfigurations { displays { width: 1080 height: 1920 dpi: 480 } userConfigurable: 3 maxDisplays: 11 } }
2024-02-27 16:14:34,190 [22069012] INFO - #com.android.tools.idea.streaming.emulator.EmulatorView - Received notification: event: DISPLAY_CONFIGURATIONS_CHANGED_UI displayConfigurationsChangedNotification { displayConfigurations { displays { width: 1080 height: 1920 dpi: 480 } userConfigurable: 3 maxDisplays: 11 } }
2024-02-27 16:14:34,299 [22069121] INFO - #com.android.tools.idea.adb.AdbService - Device [emulator-5554] is offline
2024-02-27 16:14:34,306 [22069128] INFO - #com.android.tools.idea.adb.AdbService - Device [emulator-5554] is offline
2024-02-27 16:14:34,306 [22069128] INFO - #com.android.tools.idea.adb.AdbService - Device [emulator-5554] has come online
2024-02-27 16:14:34,454 [22069276] INFO - #com.android.adblib.impl.SyncSendHandler - device:serial-emulator-5554,sync:SEND - AdbInputFileChannel("/home/rleinardi/android-studio/plugins/android/resources/process-tracker-agent/native/x86_64/process-tracker") -> "/data/local/tmp/.studio/process-tracker"
2024-02-27 16:14:35,246 [22070068] WARN - #com.android.tools.idea.avdmanager.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null
2024-02-27 16:14:36,284 [22071106] WARN - #com.android.tools.idea.avdmanager.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null
2024-02-27 16:14:37,321 [22072143] WARN - #com.android.tools.idea.avdmanager.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null
2024-02-27 16:14:38,358 [22073180] WARN - #com.android.tools.idea.avdmanager.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null
2024-02-27 16:14:39,420 [22074242] WARN - #com.android.tools.idea.avdmanager.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null
2024-02-27 16:14:40,461 [22075283] WARN - #com.android.tools.idea.avdmanager.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null
2024-02-27 16:14:41,327 [22076149] INFO - Emulator: Nexus 5 API 34 Play - Boot completed in 15088 ms
2024-02-27 16:14:41,327 [22076149] INFO - Emulator: Nexus 5 API 34 Play - Booted notification event: booted { time: 15088 }
2024-02-27 16:14:41,328 [22076150] INFO - Emulator: Nexus 5 API 34 Play - Increasing screen off timeout, logcat buffer size to 2M.
2024-02-27 16:14:41,328 [22076150] INFO - #com.android.tools.idea.streaming.emulator.EmulatorView - Received notification: 5: { 1: 15088 }
2024-02-27 16:14:45,220 [22080042] INFO - #c.i.o.a.i.PopupMenuPreloader - 24863 ms since showing to preload popup menu 'Project View Popup Menu' at 'ProjectViewPopup(preload-bgt)' in 4 ms
2024-02-27 16:14:50,012 [22084834] INFO - #com.android.tools.idea.adb.AdbService - Device [emulator-5554] has come online
2024-02-27 16:14:50,056 [22084878] INFO - #com.android.ddmlib - Device 'Nexus_5_API_34_Play [emulator-5554]' tracking jdwp process (pid=1963)
2024-02-27 16:14:50,056 [22084878] INFO - #com.android.ddmlib - Device 'Nexus_5_API_34_Play [emulator-5554]' jdwp process '1963' is now known as pkg='com.veeva.link.workflow.debug' (proc='com.veeva.link.workflow.debug')
2024-02-27 16:14:54,851 [22089673] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:54.851309 1586753 VkDecoderGlobalState.cpp:444] Creating Vulkan instance for app: Chromium
2024-02-27 16:14:54,938 [22089760] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:54.938461 1586753 VkDecoderGlobalState.cpp:1279] Created new VkDevice. ASTC emulation? 0. CPU decoding? 0
2024-02-27 16:14:57,460 [22092282] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:57.460351 1587520 VkDecoderGlobalState.cpp:1559] gfxstream_texture_format_manifest: VK_FORMAT_R8G8B8A8_UNORM
2024-02-27 16:14:58,058 [22092880] INFO - Emulator: Nexus 5 API 34 Play - I0227 16:14:58.058786 1586753 VkDecoderGlobalState.cpp:1559] gfxstream_texture_format_manifest: VK_FORMAT_R8_UNORM
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - error: kvm run failed Bad address
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - RAX=000071d60b76e000 RBX=000071d60c53925c RCX=0000000000000001 RDX=0000000000000040
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - RSI=000071d60c53925c RDI=000071d60b76e000 RBP=0000000000000008 RSP=000071d61906d9e0
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - R8 =0000000000000001 R9 =0000000000000008 R10=000000000000398e R11=a0761d6478bd642f
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - R12=0000000000000040 R13=000071d60b76e000 R14=0000000000000000 R15=0000000000000001
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - RIP=000071d9260c7997 RFL=00010246 [---Z-P-] CPL=3 II=0 A20=1 SMM=0 HLT=0
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - ES =0000 0000000000000000 ffffffff 00c00000
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - CS =0033 0000000000000000 ffffffff 00a0fb00 DPL=3 CS64 [-RA]
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - SS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA]
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - DS =0000 0000000000000000 ffffffff 00c00000
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - FS =0000 000071d619070000 ffffffff 00c00000
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - GS =0000 000071d752982950 ffffffff 00c00000
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - LDT=0000 0000000000000000 ffffffff 00c00000
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - TR =0040 fffffe0000003000 00004087 00008b00 DPL=0 TSS64-busy
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - GDT= fffffe0000001000 0000007f
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - IDT= fffffe0000000000 00000fff
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - CR0=80050033 CR2=000071d60eec2a58 CR3=000000004c0ad000 CR4=000406b0
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - DR6=00000000ffff0ff0 DR7=0000000000000400
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - EFER=0000000000000d01
2024-02-27 16:14:58,062 [22092884] INFO - Emulator: Nexus 5 API 34 Play - Code=0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 54 16 f0 f3 0f 6f 5c 16 e0 <f3> 0f 7f 07 f3 0f 7f 4f 10 f3 0f 7f 54 17 f0 f3 0f 7f 5c 17 e0 e9 7f 04 00 00 48 81 fa 80
2024-02-27 16:14:58,256 [22093078] INFO - #com.android.ddmlib - Device 'Nexus_5_API_34_Play [emulator-5554]' jdwp process '1963' is now known as pkg='com.veeva.link.workflow.debug' (proc='com.veeva.link.workflow.debug')
2024-02-27 16:15:01,591 [22096413] INFO - #o.j.p.t.LocalTerminalDirectRunner - Started com.pty4j.unix.UnixPtyProcess in 69 ms from [/bin/bash, --rcfile, /home/rleinardi/android-studio/plugins/terminal/shell-integrations/bash/bash-integration.bash, -i] in /home/rleinardi/Workspace/Misc/MyApplication, [columns=334, rows=15], diff_envs={FIG_JETBRAINS_SHELL_INTEGRATION=1, TERM=xterm-256color, TERMINAL_EMULATOR=JetBrains-JediTerm, TERM_SESSION_ID=646fd8d5-f526-44a8-b749-e24575b44597, __INTELLIJ_COMMAND_HISTFILE__=/home/rleinardi/.cache/Google/AndroidStudio2023.2/terminal/history/My Application-history1}
2024-02-27 16:15:15,608 [22110430] INFO - #c.i.o.a.i.PopupMenuPreloader - 3880 ms since showing to preload popup menu 'Edit' at 'MainMenu(preload-bgt)' in 1 ms
2024-02-27 16:15:15,608 [22110430] INFO - #c.i.o.a.i.PopupMenuPreloader - 3880 ms since showing to preload popup menu 'File' at 'MainMenu(preload-bgt)' in 1 ms
2024-02-27 16:15:15,609 [22110431] INFO - #c.i.o.a.i.PopupMenuPreloader - 3881 ms since showing to preload popup menu 'Window' at 'MainMenu(preload-bgt)' in 2 ms
2024-02-27 16:15:15,610 [22110432] INFO - #c.i.o.a.i.PopupMenuPreloader - 3882 ms since showing to preload popup menu 'Navigate' at 'MainMenu(preload-bgt)' in 3 ms
2024-02-27 16:15:15,610 [22110432] INFO - #c.i.o.a.i.PopupMenuPreloader - 3882 ms since showing to preload popup menu 'Help' at 'MainMenu(preload-bgt)' in 3 ms
2024-02-27 16:15:15,611 [22110433] INFO - #c.i.o.a.i.PopupMenuPreloader - 3883 ms since showing to preload popup menu 'Ru

bo...@google.com <bo...@google.com> #172Feb 27, 2024 03:24PM

/home/rleinardi/android-sdk/emulator-old/emulator

you can move out the /home/rleinardi/android-sdk/emulator-old/package.xml from that, and then put the newer one at /home/rleinardi/android-sdk/emulator/, and copy the package.xml to /home/rleinardi/android-sdk/emulator/

le...@gmail.com <le...@gmail.com> #173Feb 27, 2024 04:09PM

Hey thanks, now AS uses the same version as if I start it from command line.

ko...@google.com <ko...@google.com> #174Mar 20, 2024 04:12PM

Marked as fixed.

I believe the issues on both AMD and Intel side are now resolved with recent changes and default feature flags.
I'm closing this one as I cannot repro any similar issues, but feel free to reopen or file a new ticket if you're still experiencing black screens or freeze issues on Chome with the canary Emulator.

Thanks

ca...@google.com <ca...@google.com> #175Mar 20, 2024 07:03PM

Status: Assigned (reopened)

Tried this on an Ubuntu machine with an AMD APU with RDNA3 graphics and it still crashes on emu 35.1.1-11577608 when opening chrome. On an Arch with RDNA2 it still freezes.

Here's a crash report ID: c93fcb003eb008a7

2024-03-20 11-44-03.mp4

3.1 MB

Download

idea (1).log

1.7 MB

View

Download

ko...@google.com <ko...@google.com> #176Mar 25, 2024 05:44PM

Catly, according to the log attached, that instance is switching to software rendering, can you please try enforcing hardware/host GPU and let me know if it'll make a difference?
Logs suggests an unbox_VkImage operation is failing, but it's not clear to me if that's related to some unsupported path with swiftshader.

2024-03-14 13:53:43,840 [ 660622]   WARN - Emulator: Pixel Fold API 34 - Your GPU drivers may have a bug. Switching to software rendering.
2024-03-14 13:53:43,840 [ 660622]   INFO - Emulator: Pixel Fold API 34 - library_mode swangle_indirect gpu mode swangle_indirect
2024-03-14 13:53:43,841 [ 660623]   INFO - Emulator: Pixel Fold API 34 - Initializing hardware OpenGLES emulation support
2024-03-14 13:53:44,216 [ 660998]   INFO - Emulator: Pixel Fold API 34 - android_startOpenglesRenderer: gpu infoI0314 13:53:44.216145    6531 HealthMonitor.cpp:279] HealthMonitor disabled.
2024-03-14 13:53:44,216 [ 660998]   INFO - Emulator: Pixel Fold API 34 - cannot add library /home/catly/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
2024-03-14 13:53:44,216 [ 660998]   INFO - Emulator: Pixel Fold API 34 - cannot add library /home/catly/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so.1: failed
2024-03-14 13:53:44,249 [ 661031]   INFO - Emulator: Pixel Fold API 34 - added library /home/catly/Android/Sdk/emulator/lib64/vulkan/libvulkan.so
2024-03-14 13:53:44,403 [ 661185]   INFO - Emulator: Pixel Fold API 34 - createGlobalVkEmulation:995 Selecting Vulkan device: SwiftShader Device (Subzero)
2024-03-14 13:53:44,442 [ 661224]   INFO - Emulator: Pixel Fold API 34 - initialize: Supports id properties, got a vulkan device UUID

ca...@google.com <ca...@google.com> #177Mar 25, 2024 06:56PM

When I run it in the terminal with -gpu host, the issue still repros.

verbose (3).txt

41 KB

View

Download

ga...@gmail.com <ga...@gmail.com> #178Mar 28, 2024 02:38AM

I could never get it to work, but installing firefox and using that instead is a good alternative

ko...@google.com <ko...@google.com> #179Mar 28, 2024 09:55AM

We have made some changes (aosp/3014040) to ensure the flags are propagated correctly to the rendering operations and the issues on Intel and AMD should be resolved with the latest builds.
For the software rendering case, I'm unable to repro with the latest.

Carlos, can you try testing with -gpu host, -gpu swangle and -gpu swiftshader flags separately with the latest (build id > 11635764) and let me know if there are still crashes? Thank you

ca...@google.com <ca...@google.com> #180Apr 1, 2024 06:06PM

For build 11650704, it still freezes when using -gpu host but it's not freezing with -gpu swangle and -gpu swiftshader.

2024-04-01 10-45-37.mp4

1.8 MB

Download

verbose (4).txt

39 KB

View

Download

ko...@google.com <ko...@google.com> #181Apr 2, 2024 01:08PM

I can see the VulkanAllocateDeviceMemoryOnly option is enabled for that device, but it's a different AMD gpu and it's still not working. It'll take time to solve it properly without getting a repro locally. I'll add another workaround for switching to swiftshader for that GPU model.

ko...@google.com <ko...@google.com> #182Apr 4, 2024 05:29PM

A CL is uploaded to fix the issues on that specific AMD Custom GPU, I will close the issue with emulator build links once it is submitted and please reopen if the issue still persists.

This ticket has been used for many Chrome related issues from different devices, would be better to create separate tickets for new host devices and GPUs, to help implement and track the fixes more efficiently.

ko...@google.com <ko...@google.com> #183Apr 5, 2024 07:15AM

Marked as fixed.

Freeze issues on the AMD Custom GPU should be fixed with the new builds, please try: https://android-build.corp.google.com/artifact/submitted/11675956/emulator-linux_x64_gfxstream/latest/view/sdk-repo-linux-emulator-11675956.zip

mt...@gmail.com <mt...@gmail.com> #184May 17, 2024 06:10AM

When starting the latest emulator (which supposedly includes a fix for this issue, https://developer.android.com/studio/releases/emulator) on an Ubuntu 22.04 host:

Android emulator version 34.2.13.0 (build_id 11772612) (CL:N/A)

with an AVD with the following properties

avd.ini.displayname              Pixel Tablet API VanillaIceCream
avd.ini.encoding                 UTF-8
AvdId                            Pixel_Tablet_API_VanillaIceCream
disk.dataPartition.size          6442450944
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.device.hash2                  MD5:3eb16c85159ad6e1cbb3263194d1a735
hw.device.manufacturer           Google
hw.device.name                   pixel_tablet
hw.dPad                          no
hw.gps                           no
hw.gpu.enabled                   yes
hw.gpu.mode                      auto
hw.initialOrientation            landscape
hw.keyboard                      yes
hw.lcd.density                   320
hw.lcd.height                    1600
hw.lcd.width                     2560
hw.mainKeys                      no
hw.ramSize                       2048
hw.sdCard                        yes
hw.sensors.orientation           yes
hw.sensors.proximity             no
hw.trackBall                     no
image.androidVersion.api         34
image.androidVersion.codename    VanillaIceCream
image.sysdir.1                   system-images/android-VanillaIceCream/google_apis_playstore/x86_64/
PlayStore.enabled                true
runtime.network.latency          none
runtime.network.speed            full
showDeviceFrame                  yes
skin.dynamic                     yes
tag.display                      Google Play
tag.displaynames                 Google Play
tag.id                           google_apis_playstore
tag.ids                          google_apis_playstore
vm.heapSize                      192

Chrome still crashes the emulator:

I0517 08:08:55.024747 680611 VkDecoderGlobalState.cpp:631] Creating Vulkan instance for app: Chromium I0517 08:08:55.088433 680611 VkDecoderGlobalState.cpp:1482] Created new VkDevice. ASTC emulation? 0. CPU decoding? 0 Segmentation fault (core dumped)

With

Vulkan = off
GLDirectMem = on

in advancedFeatures.ini, emulator does not crash, but pages are not rendered correctly, neither in Chrome app, nor Chrome custom tabs.

Message last modified on May 17, 2024 06:28AM

ya...@google.com <ya...@google.com> #185May 20, 2024 04:54PM

Hi,

after it crashes, would you help to run the command:

/path/to/emulator/crashreport -u

And send us the crash report ID? Thanks.

wo...@gmail.com <wo...@gmail.com> #186Jun 5, 2024 11:40PM

Comment has been deleted.

Message last modified on Oct 17, 2024 06:57PM

unnamed.png

18 KB

View

Download

Issue 225541819

Description

Issue summary

Comments

hu...@google.com <hu...@google.com> Mar 22, 2022 08:13PM

bo...@google.com <bo...@google.com> Mar 23, 2022 06:45PM

ya...@google.com <ya...@google.com> #2Mar 23, 2022 09:15PM

jb...@gtempaccount.com <jb...@gtempaccount.com> #3Mar 24, 2022 03:49PM

ya...@google.com <ya...@google.com> #4Mar 24, 2022 05:59PM

jb...@gtempaccount.com <jb...@gtempaccount.com> #5Mar 29, 2022 07:53AM

ya...@google.com <ya...@google.com> #6Mar 29, 2022 07:02PM

ya...@google.com <ya...@google.com> #7Mar 29, 2022 07:02PM

jb...@gtempaccount.com <jb...@gtempaccount.com> #8Mar 30, 2022 01:50PM

ya...@google.com <ya...@google.com> #9Mar 30, 2022 04:34PM

jb...@gtempaccount.com <jb...@gtempaccount.com> #10Mar 30, 2022 06:37PM

ya...@google.com <ya...@google.com> #11Mar 30, 2022 09:32PM

ni...@gmail.com <ni...@gmail.com> #12Nov 3, 2022 05:44PM

sa...@exalt.ps <sa...@exalt.ps> #13Nov 22, 2022 10:49AM

ya...@google.com <ya...@google.com> #14Nov 22, 2022 06:31PM

rv...@gmail.com <rv...@gmail.com> #15Nov 28, 2022 07:14PM

le...@gmail.com <le...@gmail.com> #16Dec 20, 2022 10:47AM

ya...@google.com <ya...@google.com> #17Dec 20, 2022 06:05PM

[Deleted User] <[Deleted User]> #18Dec 27, 2022 04:19PM

su...@innomatic.ca <su...@innomatic.ca> #19Dec 28, 2022 06:22PM

da...@gmail.com <da...@gmail.com> #20Dec 30, 2022 05:58PM

iv...@gmail.com <iv...@gmail.com> #21Jan 9, 2023 09:50PM

cc...@logitech.com <cc...@logitech.com> #22Jan 17, 2023 03:53PM

ya...@google.com <ya...@google.com> #23Jan 17, 2023 10:05PM

ca...@google.com <ca...@google.com> #24Jan 20, 2023 12:10AM

ya...@google.com <ya...@google.com> #25Jan 20, 2023 12:17AM

ya...@google.com <ya...@google.com> #26Jan 20, 2023 12:21AM

aw...@google.com <aw...@google.com> #27Jan 20, 2023 02:41PM

ca...@google.com <ca...@google.com> #28Jan 25, 2023 12:46AM

wb...@gmail.com <wb...@gmail.com> #29Jan 26, 2023 03:43PM

ya...@google.com <ya...@google.com> #30Jan 26, 2023 06:11PM

wb...@gmail.com <wb...@gmail.com> #31Feb 7, 2023 09:21AM

wb...@gmail.com <wb...@gmail.com> #32Feb 9, 2023 10:41AM

le...@gmail.com <le...@gmail.com> #33Feb 21, 2023 08:20AM

aw...@google.com <aw...@google.com> #34Feb 27, 2023 05:52PM

aw...@google.com <aw...@google.com> #35Mar 9, 2023 06:13PM

le...@gmail.com <le...@gmail.com> #36Mar 17, 2023 11:07AM

oe...@gmail.com <oe...@gmail.com> #37Mar 17, 2023 07:11PM

jo...@spork.tech <jo...@spork.tech> #38Mar 31, 2023 02:15PM

ro...@veeva.com <ro...@veeva.com> #39Apr 11, 2023 11:28AM

aw...@google.com <aw...@google.com> #40Apr 11, 2023 02:02PM

ja...@gmail.com <ja...@gmail.com> #41Apr 11, 2023 02:03PM

ro...@veeva.com <ro...@veeva.com> #42Apr 11, 2023 02:05PM

aw...@google.com <aw...@google.com> #43Apr 11, 2023 02:08PM

ro...@veeva.com <ro...@veeva.com> #44Apr 11, 2023 02:13PM

hs...@google.com <hs...@google.com> #45Jun 28, 2023 06:35PM

pc...@gmail.com <pc...@gmail.com> #46Jul 1, 2023 11:15AM

t9...@gmail.com <t9...@gmail.com> #47Jul 6, 2023 08:10AM

le...@gmail.com <le...@gmail.com> #48Jul 8, 2023 02:00PM

hs...@google.com <hs...@google.com> #49Jul 10, 2023 11:21PM

hs...@google.com <hs...@google.com> #50Jul 11, 2023 05:14PM

ed...@gmail.com <ed...@gmail.com> #51Aug 31, 2023 09:04AM

ya...@google.com <ya...@google.com> #52Aug 31, 2023 05:32PM

bo...@google.com <bo...@google.com> #53Sep 12, 2023 02:19AM

hs...@google.com <hs...@google.com> #54Sep 13, 2023 04:41PM

ya...@google.com <ya...@google.com> Sep 13, 2023 06:24PM

hs...@google.com <hs...@google.com> #55Sep 14, 2023 08:13PM

bo...@google.com <bo...@google.com> #56Sep 14, 2023 10:57PM

hs...@google.com <hs...@google.com> #57Sep 14, 2023 11:18PM

hs...@google.com <hs...@google.com> #58Sep 14, 2023 11:21PM

hs...@google.com <hs...@google.com> #59Sep 14, 2023 11:35PM

bo...@google.com <bo...@google.com> #60Sep 14, 2023 11:38PM

rk...@google.com <rk...@google.com> #61Sep 14, 2023 11:39PM

bo...@google.com <bo...@google.com> #62Sep 14, 2023 11:41PM

hs...@google.com <hs...@google.com> #63Sep 14, 2023 11:42PM

hs...@google.com <hs...@google.com> #64Sep 14, 2023 11:45PM

rk...@google.com <rk...@google.com> #65Sep 14, 2023 11:46PM

hs...@google.com <hs...@google.com> #66Sep 14, 2023 11:49PM

hs...@google.com <hs...@google.com> #67Sep 14, 2023 11:53PM

rk...@google.com <rk...@google.com> #68Sep 15, 2023 04:30AM

ya...@google.com <ya...@google.com> #69Sep 15, 2023 05:00PM

bo...@google.com <bo...@google.com> #70Sep 15, 2023 06:20PM

hs...@google.com <hs...@google.com> #71Sep 15, 2023 07:10PM

hs...@google.com <hs...@google.com> #72Sep 15, 2023 07:16PM

bo...@google.com <bo...@google.com> #73Sep 15, 2023 10:38PM

hs...@google.com <hs...@google.com> #74Sep 18, 2023 04:39PM