FrameNavigationEntry(s) for frames created by scripts are only useful while their frame stays alive - when such frames are (re)created they always get a fresh, random, unique name (that therefore never matches old FrameNavigationEntry(s) from the previous reincarnation of the frame).

This problem is to a large extend addressed by https://crrev.com/c/767627, but it only prunes FNEs from the *current* NavEntry.  This bug tracks the remaining work of pruning FNEs from *all* NavEntries.

See also
-  issue 784356  (performance impact of not pruning)
- issue 373041 (desire to share FNEs across NavEntries)
- https://chromium-review.googlesource.com/c/chromium/src/+/767627/5/content/browser/frame_host/frame_tree_node.cc#243
 

FrameNavigationEntry(s) for frames created by scripts are only useful while their frame stays alive - when such frames are (re)created they always get a fresh, random, unique name (that therefore never matches old FrameNavigationEntry(s) from the previous reincarnation of the frame).

This problem is to a large extent addressed by https://crrev.com/c/767627, but it only prunes FNEs from the *current* NavEntry.  This bug tracks the remaining work of pruning FNEs from *all* NavEntries.

See also
-  issue 784356  (performance impact of not pruning)
- issue 373041 (desire to share FNEs across NavEntries)
- https://chromium-review.googlesource.com/c/chromium/src/+/767627/5/content/browser/frame_host/frame_tree_node.cc#243