Frame Profile : "Initializing" after click start trace and can not start capture trace. I notice the application is relaunched.

[Ed1sonzZ]

Environment information:

• AGI version:
• Host OS: [e.g. Linux] If tracing on Android:
• Device model:
• Android Version:

Bug description A clear and concise description of what the bug is.

Reproduction steps Steps to reproduce the behavior:

Stacktrace Please paste a stacktrace here if it's available.

Screenshots If applicable, add screenshots to help explain your problem.

Additional debugging information

• Please attach the generated gapis.log and gapic.log files you will find in the temp folder (e.g. /tmp/ on linux).
• If using Android: Please attach a full logcat dump (adb logcat -d > logcat-full.txt) that contains logs since AGI was started.

[t1u1]

Same here.

AGI version: 2.1.0 Device: Pixel 4a Android: 12, Build number SQ1A.220105.002

System trace works, but Frame trace using OpenGL + ANGLE is stuck in "Initializing" state.

Angle version: 15789_angle-arm_64.apk

[t1u1]

In the logcat of the device, this message is repeated continuously while AGI is active:

failed to connect to socket 'localabstract:gapii': could not connect to localabstract address 'localabstract:gapii'

[ttanatb]

Hi, thanks for filing the issue (and apologies for the untimely response) -- there's some scenarios in which AGI silently fails without the best information for how to triage, and we're working to improve this.

One likely scenario occurs when the application launches multiple processes and AGI mistakenly attaches itself to a process that does not make draw calls, leaving the phone at a blank screen. In that case, add the exact process name in the trace dialog (seen below), and AGI will attach itself to the correct process.

If this is not the issue you're encountering, then please provide more context / logs that will help me triage and figure out what's going on :)

[hillli007]

@ttanatb I have the same problem, and my scenario is not multiple processes. Has the problem been solved?

[ttanatb]

We've seen issues with Frame Profiling not working against specific applications, but this is often a case by case basis. @hillli007 Please feel free to open a new issue (or re-open this) with more information, context, logs. (gapis.log gapic.log and result from adb logcat -d > logcat-full.txt)