Menu
Who Do Is
  • Home
  • What
  • How
  • Is
  • Can
  • Are
  • Does
  • Do
  • Why
  • Who
  • Where
  • Which
  • Which
  • Should
  • Will
  • When
  • What’s
  • Did
Who Do Is

[ANSWERED] java – How to solve “Waiting until last debugger command completes” stuck in Android Studio?

Posted on November 14, 2022

Solution 1 :

I’ve this issue for a few months with Idea 2020.2 + android plugin and, in my case, I resolved by disabling:

Settings -> Debugger -> Data Views -> Java -> Enable alternative view for Collections classes (enabled by default)

and

Settings -> Debugger -> Data Views -> Java -> Enable ToString object view (enabled by default)

as recommended by this comment

Problem :

My project is in Android Studio. It has around 35 thousand lines in a Windows 7. My environment is updated. I use Kotlin and not Java, but it’s not important. I have lot of memory in my computer.

I read all material in Internet about the message Waiting until last debugger command completes while debuggng my app in the cell phone.

For me, the debugger works in normal pace, or it stucks (hangs) completely, or sometimes it’s very slow.

I have threads in my app, but many times this problem occurs outside of any thread. Just in plain code!

I’ve posted it as a bug in Google Issue Tracker and JetBrains, including the dump file and idea.log file. Google has stamped the priority as P3 and severity as S3 (low levels). JetBrains have answered me and I’ve produced many dumps and screenshots. They have claimed that the problem can only be Google‘s. Too much time has passed with no more positioning by JetBrains but today (Out/2) Andrei Kuznetsov from JetBrains has given me one suggestion (item f below)

Possible workarounds that can’t solve my problem:

a) Erase all watch variables. Improves a little bit.

b) Erase old breakpoints. It’s not enough.

READ  [ANSWERED] android - Flutter Row() - Align 3 widgets evenly
Powered by Inline Related Posts

c) Execute Invalidate Caches and Restart

d) Uncheck Enable ToString object view in Settings, Build,Execution and Deployment, Debugger, Data Views, Java

e) Disable JIT is unchecked in Debugger settings

f) I try to disable the option Force classic VM for JDK 1.3x and earlier in Debugger settings, but it also doesn’t work.

g) 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.

h) During running, in debug window, click in some variable with right mouse button, and select Mute Rendering, that generates a big overhead in debuggin session. It was saved for future sessions. (JetBrains suggestion)

i) Now I’m trying go to Settings -> Debugger -> Data Views -> Java and disable the option Enable alternative view for Collections classes (From fireb86 answer). Let’s see what happens.

-/-

There are JetBrains reports about this problem since 2008!

Disclaimer: It contains many updates I since I’ve asked the original question. I join all information to make reading this issue more fluid.

Comments

Comment posted by Gazzx

Any solution? I’m stuck with the same problem for the last few hours and I can’t debug my app.

Comment posted by Paulo Buchsbaum

They (Jet Brains and Google) are ignoring the issue tracker that I’ve posted.

Comment posted by Gazzx

I downgraded my android studio from 4.2 to 4.1 and everything was working again.

Comment posted by Paulo Buchsbaum

I am impressed by their disregard for users.

Comment posted by Paulo Buchsbaum

1)

Comment posted by fireb86

@PauloBuchsbaum I edited my solution because the debugger works well with breakpoints with both “Suspend: Thread” and “Suspend: All” so I suppose the guilty is “Enable alternative view for Collections classes”

READ  [ANSWERED] android error in flutter with no specific errors
Powered by Inline Related Posts

Comment posted by Paulo Buchsbaum

I will try this for some time and I will report here the results.

Comment posted by Paulo Buchsbaum

I’d made an update in my question based on your suggestion. I need some time to check if it solves the problem.

Comment posted by DSlomer64

Since the problem persists in Arctic Fox and (AFAIK) the menu flow is now nothing like it was in Nov 2020, I’ll point out that

Recent Posts

  • How can I play with my cat without toys?
  • What is a bag pipe band called?
  • Are Honda Civics actually fast?
  • Are Yankee candles toxic?
  • How do I pair my Michael Kors smartwatch with my Android?

Recent Comments

No comments to show.

Archives

  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022

Categories

  • ¿Cómo
  • ¿Cuál
  • ¿Cuántas
  • ¿Cuánto
  • ¿Que
  • ¿Quién
  • 90” and 108” so you may have to round up to the nearest size.
  • and delete any Spotify folders from it. Once this is done
  • Android
  • Are
  • At
  • Bei
  • blink
  • C'est
  • Can
  • carbs
  • Comment
  • Did
  • Do
  • Does
  • During
  • For
  • Has
  • How
  • In
  • Is
  • Ist
  • Kann
  • Können
  • nouveau
  • On
  • or 108 inches.2020-08-03
  • Où
  • owning
  • Pourquoi
  • Puis-je
  • Quand
  • Quante
  • Quel
  • Quelle
  • Quelles
  • Quels
  • Qui
  • Should
  • Sind
  • Sollte
  • spiritual
  • tap the downward-facing arrow on the top left. A downward-facing arrow will appear underneath each song in the album; they'll turn green as the download completes.2020-07-28
  • Uncategorized
  • Wann
  • Warum
  • Was
  • Welche
  • Welcher
  • Welches
  • Welke
  • Wer
  • Were
  • What
  • What's
  • When
  • Where
  • Which
  • Who
  • Whose
  • Why
  • Wie
  • Will
  • Wo
  • Woher
  • you will receive two curtains each with the same measurements of width 66"" (168cm) x drop 54""(137cm).
  • you'll see a green downward-facing arrow next to each song.2021-02-26
©2023 Who Do Is | Powered by SuperbThemes & WordPress