Fixed
Status Update
No update yet.
Comments
jb...@google.com
pr...@google.com
I'll try to get more details, but wanted to bring it up at least.
Please specify your OS, CPU, GPU, the emulator version, the system image you use and how your start the emulator (standalone or embedded into AS).
ty...@gmail.com
I'm experiencing same issue. It happened randomly, the most often it froze after I resized the emulator window.
I'm on Macbook Pro M2 Max, MacOS Sonoma 14.1.1, Android Studio Iguana 2023.2.1 Canary 14.
I opened the emulator through the Device Manager and use the floating window emulator (not docked).
Screen record attached. The easiest way to reproduce is by resizing or zooming in/out the emulator.
I'm on Macbook Pro M2 Max, MacOS Sonoma 14.1.1, Android Studio Iguana 2023.2.1 Canary 14.
I opened the emulator through the Device Manager and use the floating window emulator (not docked).
Screen record attached. The easiest way to reproduce is by resizing or zooming in/out the emulator.
dr...@gmail.com
lb...@gmail.com
Hi okynk91, thank you for screen recording, we will investigate. I see you run the emulator in the AS window. Could you please try running it in its own window (see the attached screenshot)?
Description
Version used: 1.7.0
Devices/Android versions reproduced on: API 33
If this is a bug in the library, we would appreciate if you could attach:
Example project attached
Description:
It appears that ComponentActivity$ReportFullyDrawnExecutorApi16Impl.this$0 leaks memory when used in an ActivityScenario if the ActivityScenario is used to recreate the Activity soon after the Activity has been launched.
Reproduction steps:
1. Create an Activity that extends ComponentActivity
2. Set a content view for the Activity in the onCreate using either setContentView(View) or setContent { <Composable> }
3. Create an instrumented test that uses LeakCanary's DetectLeaksAfterTestSuccess Test Rule
4. In the test: Launch the Activity using ActivityScenario, and then call "recreate" on the ActivityScenario
5a. Expected result: The test launches the Activity, recreates it, and the test passes.
5b. Actual result: The test launches the Activity, recreates it, and then LeakCanary detects a memory leak from ComponentActivity$ReportFullyDrawnExecutorApi16Impl.this$0 leaking an instance of the Activity.
This issue does not occur for ComponentActivity instance that do not set a content view in onCreate, and does not occur for regular android.app.Activity instances.
I have attached an example project with eight instrumented tests that show case this issue. In the ExampleInstrumentedTest.kt tests `launchExampleViewActivityAndRecreate` and `launchExampleComposeActivityAndRecreate` both fail, and all other tests succeed. The expected behaviour is that all tests should pass.