Status Update
Comments
jv...@google.com <jv...@google.com>
ju...@google.com <ju...@google.com>
em...@google.com <em...@google.com> #2
I'm also seeing this issue with Material Components 1.3.0 and ConstraintLayout 2.1.0-alpha2
cm...@gmail.com <cm...@gmail.com> #3
aa...@google.com <aa...@google.com> #4
What device is this on? Specifically, what API level?
aa...@google.com <aa...@google.com> #5
Possible dup of
cm...@gmail.com <cm...@gmail.com> #6
Note: although the slow execution upon first adb installation does not occur any more on all my test devices.
However below is still happen on all the devices API tested i.e. API-21, API-24, API-28, API-29, API-33.
In the past the exact same problem happens only after the app resumes from an inline break-point. Whenever this happens, I just restart a whole new adb debug process. However the above new problem has now prevented one to do any form of useful app debug; except to dump/view the logcat message.
aa...@google.com <aa...@google.com> #7
I don't understand the last comment.
What is still happening? What is not happening?
cm...@gmail.com <cm...@gmail.com> #8
1. Note: although the slow execution upon first adb installation does not occur any more on all my test devices.
This refers to the issue referred to: Possible dup of [
i.e. the problem described in my first comment..
"About 2 days ago, for unexplained reason after a fresh adb installation, the app debug execution speed is running at an extremely slow pace; it even causes aTalk login process to timeout on a 30-seconds timer; this was never happened before.
This slow execution speed persists throughout the whole debug process. When the USB debug cable is detached (no adb debug process is attached) , everything returns to normal operation."
2. However below problem is still happening on all the devices API tested i.e. API-21, API-24, API-28, API-29, API-33.
In the past the "exact same problem" happens only after the app resumes from an inline break-point.
Whenever this happens, I just restart a whole new adb debug session. However this slow execution problem has prevented one to do any form of useful app debug; except to dump/view the logcat message.
The "exact same problem" refers to slow debug execution.
aa...@google.com <aa...@google.com> #9
Are you saying that it takes a long time to resume from a breakpoint?
Can you attach a video?
cm...@gmail.com <cm...@gmail.com> #10
After this, it is not further practical to continue with the debug at this slow execution speed. I need to restart the app to return the app execution back to its normal pace.
To see the problem, you can download
aa...@google.com <aa...@google.com> #11
What devices are you using? Is this happening with the built-in emulators in Android Studio?
Can you confirm that it's happening on all API levels?
We are aware that is happening on AI 33 and used to happen on API 32 until it was recently patched with a fix. But in my testing, I could not reproduce this with ny other API levels.
cm...@gmail.com <cm...@gmail.com> #12
With your latest input, I need to retest them to see if the problem still exist.
I have not doing any system debug for the past 2-3 months. By the way, when the problem was since resolved.
aa...@google.com <aa...@google.com> #13
I built and installed
private void onNumberClick(View btnView) {
Random random = new Random(System.currentTimeMillis());
long now = System.currentTimeMillis();
for (int i = 0; i < 1_000_000; i++) {
Math.sin(random.nextInt());
}
Toast.makeText(this, "Time: " + (System.currentTimeMillis() - now), Toast.LENGTH_SHORT).show();
...
I don't see any slowdown when debugging with or without a breakpoint on API 31 or 32. I do see a significant slowdown on API 33 with or without a breakpoint (
cm...@gmail.com <cm...@gmail.com> #14
a. Samsung Note10+ device
b. AVD Pixel2 API-31
c. AVD Pixel 6 Pro API-33
The slow execution speed after break point do not happen on all the 3 devices. Look like the problem has been resolved.
You can close the issue for now. I will continue monitoring in future testing..
Thanks a lot for your team effort to fix the issue.
Description
AI-212.5712.43.2112.8815526, JRE 11.0.12+0-b1504.28-7817840x64 JetBrains s.r.o., OS Linux(amd64) v5.15.0-48-generic, screens 3840.0x2160.0, 2560.0x1600.0
AS: Chipmunk | 2021.2.1 Patch 2; Kotlin plugin: 212-1.7.10-release-333-AS5457.46; Android Gradle Plugin: 4.2.2; Gradle: 6.9; Gradle JDK: version 11.0.12; NDK: from local.properties: (not specified), latest from SDK: 22.1.7171670; LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: 3.18.1-g262b901, from PATH: 3.22.1
IMPORTANT: Please read
About 2 days ago, for unexplained reason after a fresh adb installation, the app debug execution speed is running at an extremely slow pace; it even causes aTalk login process to timeout on a 30-seconds timer; this was never happened before.
This slow execution speed persists throughout the whole debug process. When the USB debug cable is detached (no adb debug process is attached) , everything returns to normal operation.
In the past the exact same problem happens only after the app resumes from an inline break-point.
Whenever this happens, I just restart a whole new adb debug process. However the above new problem has now prevented one to do any form of useful app debug; except to dump/view the logcat message.
In both case, the slow app execution speed is very serious, and practically prevents anyone to perform any useful app debug.