Both `BrowsingContextWebProgress` and the static map `sBounceTrackingStates` have strong reference to `BounceTrackingState`. That means even when a tab gets destroyed and with it `BrowsingContextWebProgress` we keep `BounceTrackingState` alive. Since we create one `BounceTrackingState` per tab but don't destroy it that means we effectively leak them. For longer sessions this could have a negative impact on memory usage.
Bug 1908393 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Both `BrowsingContextWebProgress` and the static map `sBounceTrackingStates` have strong reference to `BounceTrackingState`. That means even when a tab gets destroyed and with it `BrowsingContextWebProgress` we keep `BounceTrackingState` alive. Since we create one `BounceTrackingState` per tab but don't destroy it that means we effectively leak them. For longer sessions with a lot of tabs this could have a negative impact on memory usage.