IssueTracker

Adding 2 more thread dumps from another freeze. Again after switching branches and updating from git.

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 https://developer.android.com/studio/nightly) that would be helpful -- and of course if you can trigger this in a recent nightly build, that's would be very important information.

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.

That's good to hear. I think that the fix (which for reference was https://github.com/JetBrains/intellij-community/commit/fe621544dd61a9af34d97958d3d823a7c3454a87) is effective for both beta and canary branches.

For the record I am also arranging for https://github.com/JetBrains/intellij-community/commit/a444c8a500883669fc05c7177f93b5b794fdd13b (same fix, different implementation class) to be included; it's probably inactive code in our configurations, but it might be possible to trigger nevertheless.

Thanks for the confirmation!

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!

Ucfucuccj

Hyxucyccchccjch

Ycucuccjcn

Hola mundo

RE#10 Thank you for pointing that out. Removing the ifdef is a legitmate fix. The random crash is interesting but I doubt it has to with removing ifdef. Previously the ifdef guard was there probably because we used to have migw windows target but I don't think it's there anymore.

My fix is landed in CL and the next canary and release branch will include the fix.