为每个Fragment配置Toolbar引发内存泄漏，请教移除释放方案

Great question—this is a super common pitfall when setting up per-Fragment Toolbars with a host Activity, so let’s break down exactly where and how to clean things up properly.

Why the Leak Happens #

When you attach a Fragment’s Toolbar via your Activity’s setToolbar() method, the Activity’s view hierarchy keeps a reference to that Toolbar. If the Fragment gets destroyed but the Toolbar isn’t removed:

• The Toolbar might hold a reference back to the Fragment (like click listeners using the Fragment’s context or methods)
• The Activity retains the Toolbar, which in turn stops the Fragment from being garbage collected

Where to Remove the Toolbar #

The perfect lifecycle method for this cleanup is onDestroyView() in your Fragment. Here’s why:

• It triggers when the Fragment’s view is destroyed (even if the Fragment itself isn’t fully wiped, like when it’s stored in the back stack)
• It’s the earliest safe point to clean up view-related resources, so you don’t leave orphaned references hanging around

Step-by-Step Implementation #

1. Update Your Activity’s Toolbar Management

First, tweak your Activity to support removing Toolbars and track the current active one to avoid duplicates:

// Inside your host Activity
private var currentToolbar: Toolbar? = null

// Updated setToolbar method to replace old Toolbars first
fun setToolbar(toolbar: Toolbar) {
    // Remove any existing Toolbar to prevent leaks/duplicates
    currentToolbar?.let {
        val toolbarContainer = findViewById<ViewGroup>(R.id.toolbar_container)
        toolbarContainer.removeView(it)
    }
    // Add the new Toolbar to your container layout
    val toolbarContainer = findViewById<ViewGroup>(R.id.toolbar_container)
    toolbarContainer.addView(toolbar)
    currentToolbar = toolbar
    // Optional: Set as ActionBar if your app uses it
    setSupportActionBar(toolbar)
}

// Add a method to explicitly remove the Toolbar
fun removeToolbar() {
    currentToolbar?.let {
        val toolbarContainer = findViewById<ViewGroup>(R.id.toolbar_container)
        toolbarContainer.removeView(it)
        // Disassociate from ActionBar to break another potential reference chain
        setSupportActionBar(null)
        currentToolbar = null
    }
}

2. Clean Up in the Fragment’s onDestroyView()

In every Fragment that uses a Toolbar, add logic to notify the Activity and release local references:

// Inside your Fragment
private var fragmentToolbar: Toolbar? = null // Use nullable instead of lateinit for easy cleanup

override fun onCreateView(
    inflater: LayoutInflater,
    container: ViewGroup?,
    savedInstanceState: Bundle?
): View? {
    val view = inflater.inflate(R.layout.your_fragment_layout, container, false)
    fragmentToolbar = view.findViewById(R.id.fragment_toolbar)
    // Attach the Toolbar to the Activity
    (activity as? YourHostActivity)?.setToolbar(fragmentToolbar!!)
    return view
}

override fun onDestroyView() {
    super.onDestroyView()
    // 1. Tell the Activity to remove the Toolbar
    (activity as? YourHostActivity)?.removeToolbar()
    // 2. Release the Fragment's local reference to break the chain
    fragmentToolbar = null
}

Key Tips to Prevent Future Leaks #

• Use nullable references: Skip lateinit for Fragments’ Toolbars—nullable variables let you explicitly set them to null to cut off reference chains.
• Safe Activity casts: Always use activity as? instead of a direct cast to avoid crashes if the Activity is already destroyed when the Fragment cleans up.
• Back stack compatibility: If your Fragment is added to the back stack, onDestroyView() runs when it’s pushed out, and onCreateView() re-runs when it’s popped back—this ensures the Toolbar reattaches correctly without leaks.

内容的提问来源于stack exchange，提问作者amodkanthe