IssueTracker

Jetpack Compose version: at least 1.2.0 - 1.4.0-alpha03

Jetpack Compose component(s) used: -

Android Studio Build: 2022.1.1 rc3 - 2022.2.1 Canary 11

Kotlin version: at least 1.7.20 - 1.7.21

Application consists from 3 activities. MainActivity, IntermediateActivity, ComposeActivity MainActivity was added Fragment which has basic Compose UI.

MainActivity is first activity

class MainActivity : AppCompatActivity() {

    private lateinit var binding: ActivityTabbedBinding

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        binding = ActivityTabbedBinding.inflate(layoutInflater)
        setContentView(binding.root)
        val transaction = supportFragmentManager.beginTransaction()
        transaction.replace(R.id.container, MyFragment())
        transaction.commit()
    }
}

Fragment is added to MainActivity:

class MyFragment : Fragment() {

    private var fragmentWasHidden by mutableStateOf(false)

    override fun onCreateView(
        inflater: LayoutInflater, container: ViewGroup?,
        savedInstanceState: Bundle?
    ): View {
        return ComposeView(requireContext()).apply {
            setContent {
                Box {
                    Text(
                        modifier = Modifier
                            .align(Alignment.Center)
                            .clickable {
                                startActivity(
                                    Intent(
                                        requireContext(),
                                        IntermediateActivity::class.java
                                    )
                                )
                            },
                        text = "Click this text to go further, fragmentWasHidden: ${fragmentWasHidden}",
                        color = Color.White
                    )
                }
            }
        }
    }

    override fun onStop() {
        fragmentWasHidden = true
        super.onStop()
        println("checkLog TabFragment onStop")
    }
}

Second activity: IntermediateActivity

class IntermediateActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        setContentView(R.layout.intermediate_activity)
        findViewById<TextView>(R.id.click_me).setOnClickListener {
            Intent(this, ComposeActivity::class.java).let {
                startActivity(it)
            }
        }
    }
}

Third activity which leaks just compose activity with basic UI: ComposeActivity

class ComposeActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            Box(
                modifier = Modifier
                    .fillMaxSize()
                    .background(Color.Red)
            ) {
                Text(modifier = Modifier.align(Alignment.Center), text = "Next page. Now go back!")
            }
        }
    }
}

Steps:

1. Start application, click 'Click this text to go further' in MainActivity (in MyFragment)
2. Landing on IntermediateActivity click 'Click Me'
3. When landing on ComposeActivity return back. 4.. If needed more leaked ComposeActivities we can just proceed to go forward and back, as many times as needed.

Main part here is in MyFragment

    override fun onStop() {
        fragmentWasHidden = true
        super.onStop()
        println("checkLog TabFragment onStop")
    }

fragmentWasHidden state triggers recomposition last time, when Fragment already hiding. This somehow effects all compose views further ahead even separate activities.

As many times we returned from ComposeActivity to IntermediateActivities, so many leaked ComposeActivity we can have. We can verify with profiler. I'm attaching the demo project and heap dump.

When we return back to MainActivity. All instances of Compose Activities will be magically wiped out.

The request is to provide at least some workaround for it until proper fix, because I wasn't able to find any solution to this.

Reproducibility - 100%