IssueTracker

I've explained the bug here here. It's a very old bug in Android Studio. I face this problem every single day many times. Sometimes I have to restart Android Studio to get thru the point that Android Studio stucks. Sometimes it works, sometimes doesn't. It's excruciating. Now I'm not able to reproduce the error for producing a dump, but it is a problem reported by dozens or hundreds of users. I've tried everything.

Many times it's very sluggish. Today it hangs completely with Waiting until last debugger command completes runnning my app in debugger mode, outside any thread and I've waited around 10 minutes, and I've decided to produce the dump and log files, as oriented by Google support.

So I'm posting the idea.log and the dump.txt (using JStack -l 8100 >dump.txt, where 8100 is PID, that I've found with jps -mv | findstr studio command in command line.

When I try to interrupt the Android Studio freezing pressing stop(red icon) it shows the message in a window popup: Waiting for debugger response and after a while, it gets back to normal, but I have to do the whole process again. This freeze occurs onky with 2 simple breakpoints and just one variable in watch list. I think that it's too simple to crash...

I've posted in JetBrains issue tracker,with dumps and logs, but they told me that it should be a Google responsability

Google and JetBrains has something in common: Both completely ignore this very old problem, which is reported by many users. In StackOverflow I've found this question from 2015 and in JetBrains here from 2013! There is nothing to do but painfully live with such an unpleasant problem. I have to get something off my chest so I've posted this in both issue trackers. (Google and JetBrains). JetBrain has told me in my issue tracker and after I pass the dumps and logs, that the responsibility is on Google. And what about Google? Guess what! Google says nothing .....

In this issue tracker in Google from 2015, I've read a tip about trying to change, in some breakpoint, the Suspend type from all to thread and make this option default. It was this still a valid attempt today, 5 years later?

Not ignoring you at all, actually. We've experienced this in our work as well, but we don't have a reproducible case like you're encountering.

I think one of the first things to try, if you haven't already, is to see if this still happens with a new USB cable. Also, does this happen with the emulator?

I find this awful situation almost always. I's a big part of my day. My physical device that I'm using is Samsung S20 FE. Nowadays, I'm debugging using wi-fi, no USB. Virtual emulation is so slow, i don't use it! My Android Studio is completely updated and I have no RAM memory problem and memory settings in Android Studio are Ok. Another issue is infinite evaluation window in debugging.

My personal trick is debugging some breakpoints in my source code until freeze and, after, I start debugging where it has stopped last time.

Now I'm trying a workaround proposed in the comment section in my question in StackOverflow (https://stackoverflow.com/questions/63290304/how-to-solve-waiting-until-last-debugger-command-completes-stuck-in-android-st):

I've disabled "Enable alternative view for Collections classes" and "Enable ToString object view" (File / Settings / Build, Execution, Deployment / Debugger / Data Views / Java. Addionally I've disabled "Enable auto expressions in Variables view" (File / Settings / Build, Execution, Deployment / Debugger / Data Views)

We've made a bunch of improvements to debugger performance. Are you still experiencing this issue?

Can you check with USB? ADB over wifi is not in a good state, and we're fixing that up right now.