Status Update
No update yet.
Comments
vs...@google.com
We need a reproducible test case that shows this issue.
It could also be dependent on the device, so please provide details on your device as well.
It could also be dependent on the device, so please provide details on your device as well.
vs...@google.com
For anyone else who might encounter this issue, here is a summary:
The issue shows up in one of two ways: Studio will be responsive, but the debugger will be stuck at either "Collecting Data.." or "Waiting for last debugger command to complete..". This happens on both Dalivk and ART, so all versions of the platform are affected. The issue is more prevalent with Studio 1.2, but exists on all versions of Studio.
The correct fix for this issue is in the platform. The next version of M preview is likely to have this fix (in progress CL here:https://android-review.googlesource.com/#/c/152715/ )
Until then we have some workarounds which reduce the probability of hitting this issue. So if you encounter this issue, you can try one of the following:
1. Change your breakpoint to only suspend the thread where it is hit rather than all threads. Seehttps://android-review.googlesource.com/#/c/152715/ )
2. You can turn off various settings in the debugger that invoke methods: These include:
a) inline debugging (https://www.jetbrains.com/idea/help/inline-debugging.html )
b) "Enable 'toString()' object view" (Settings | Debugger | Data Views | Java)
c) "Enable alternative view for Collections classes" (Settings | Debugger | Data Views | Java)
The 2nd option is more severe (it limits the amount of automation the debugger does for you), so we are not enabling that by default. However, if you still see the issue after changing the suspend policy to thread only, then unfortunately, you'll have to do the steps in 2 as well.
Finally, if you still see the issue after both, then that would be a new bug. Please file a new bug with a test case.
The issue shows up in one of two ways: Studio will be responsive, but the debugger will be stuck at either "Collecting Data.." or "Waiting for last debugger command to complete..". This happens on both Dalivk and ART, so all versions of the platform are affected. The issue is more prevalent with Studio 1.2, but exists on all versions of Studio.
The correct fix for this issue is in the platform. The next version of M preview is likely to have this fix (in progress CL here:
Until then we have some workarounds which reduce the probability of hitting this issue. So if you encounter this issue, you can try one of the following:
1. Change your breakpoint to only suspend the thread where it is hit rather than all threads. See
2. You can turn off various settings in the debugger that invoke methods: These include:
a) inline debugging (
b) "Enable 'toString()' object view" (Settings | Debugger | Data Views | Java)
c) "Enable alternative view for Collections classes" (Settings | Debugger | Data Views | Java)
The 2nd option is more severe (it limits the amount of automation the debugger does for you), so we are not enabling that by default. However, if you still see the issue after changing the suspend policy to thread only, then unfortunately, you'll have to do the steps in 2 as well.
Finally, if you still see the issue after both, then that would be a new bug. Please file a new bug with a test case.
Description
When you push the button (screen or screen_1), it freezes (screen_2)