Status Update
No update yet.
Comments
lb...@gmail.com
mk...@google.com
bo...@google.com
lb...@gmail.com
Adding 2 more thread dumps from another freeze. Again after switching branches and updating from git.
wd...@google.com
Thanks for the report. I believe that this is fixed in our development branch, and also in the branch that will become Ladybug Feature Drop Beta. If you could verify that this doesn't happen in a nightly build (from
lb...@gmail.com
Sorry, I have not tried it on the nightly build, but since then I updated to Meerkat and I have not seen the freeze afterwards.
wd...@google.com
That's good to hear. I think that the fix (which for reference was
For the record I am also arranging for
Thanks for the confirmation!
wd...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 RC 1
- Android Gradle Plugin 8.8.0-rc01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
lb...@gmail.com
Ucfucuccj
lb...@gmail.com
Hyxucyccchccjch
lb...@gmail.com
Hola mundo
wd...@google.com
Found the root cause when the "call device" button was unresponsive. It became unresponsive because the inbound call failed to initialize. Basically, the modem simulator's shared FD failed. When receive_inbound_call is invoked, it is supposed to make connection to the "host server" via a shared fd but it is flaky on Windows unfortunately.
modem-simulator: receive_inbound_call:101 inbound call from 6505551212
modem-simulator: process_msgs:296 waiting for new messages ...
modem-simulator: main_host_thread:501 got connection at host server at 65094
modem-simulator: start_calling_thread:254 making a connection to main host server 65094
modem-simulator: main_host_thread:507 Detected close from the other side
modem-simulator: start_calling_thread:262 nothing read quit
modem-simulator: main_host_thread:494 looping at main host server at 65094
modem-simulator: start_calling_thread:284 done with this thread
lb...@gmail.com
@11 So it could be the same reason that this bug occurs:
?
wd...@google.com
RE#12 I have uploaded a
lb...@gmail.com
Have you tested it on all API versions, to make sure that it doesn't cause new issues, and also fixes the issue on other places in case it's there too?
wd...@google.com
RE#14 This issue is for API 31+, I will check for API 32 and API 33. Thanks for reminding me.
lb...@gmail.com
wd...@google.com
lb...@gmail.com
When will the fix be available?
wd...@google.com
The fix has been merged in both 31 release and 32 release for since 05/2022.
lb...@gmail.com
On which version ?
Description
1. Start emulator API 31.
2. On the "phone" page of "extended controls" window, choose "call device". Then end the call.
3. Try step 2 multiple times.
The bug is that eventually it will ignore pressing the button sometimes.
------------------
Studio Build:
Version of Gradle Plugin:
Version of Gradle:
Version of Java:
OS:
Android Studio Bumblebee | 2021.1.1 Patch 3
Build #AI-211.7628.21.2111.8309675, built on March 16, 2022
Runtime version: 11.0.11+9-b60-7590822 amd64
VM: OpenJDK 64-Bit Server VM by Oracle Corporation
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 8048M
Cores: 12
Registry: external.system.auto.import.disabled=true, ide.settings.move.mouse.on.default.button=true, debugger.watches.in.variables=false
Non-Bundled Plugins: GenerateSerialVersionUID (3.0.3), GenerateSerializationHelpers (1.0.6), Show As ... (1.0.3), com.dubreuia (2.2.0), com.github.beansoft.jadx.gui.idea (2021.2.1), com.intellij.marketplace (211.7628.36), String Manipulation (9.4.0), com.tabnine.TabNine (0.6.1), org.jetbrains.kotlin (211-1.6.21-release-334-AS7442.40), com.google.mad-scorecard (1.2), com.ppismerov.ksvu (0.0.1), net.aquadc.mike.plugin (0.22), izhangzhihao.rainbow.brackets (6.23), org.intellij.plugins.markdown (211.7142.37)