On Back-Forward navigation, the forward content process remains alive as an "invisible tab" until you manually minimize memory
Categories
(Core :: DOM: Navigation, enhancement)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
()
Details
Attachments
(2 files)
STR thar repros 90% of the time:
1.Go to https://bugzilla.mozilla.org/show_bug.cgi?id=1530397 (Call it TabA/ProcessA)
2.Click on the mozdev servo link that is in the comment 0 (Such that the demo opens in TabA but a new process ProcessB is created)
4.Let TabA/ProcessB be in the foreground for 30-45 seconds
(The memory will increase, but ignore that)
5. Click on the Back button to navigate back to the original bug page (TabA/ProcessA)
AR: 90% of the time, the ProcessB will remain alive and can be seen in Windows Task Manager. It will not go away on its own.
- Now, go to about:memory and click on minimize memory.
AR: The memory of ProcessB will shoot up to 2x (which in itself seems like a bug), then it will reduce. Finally, ProcessB will close.
10% of the time, when you navigate back (step5), the ProcessB will immediately close.
I was able to repro on a build from 2 years back, so this is not a recent regression.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
|
||
| Reporter | ||
Comment 2•3 years ago
|
||
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Updated•3 years ago
|
Comment 3•3 years ago
|
||
I'm pretty sure this is intentional behavior. It is known as the "BFCache" (for backwards-forwards). It improves navigation speed when navigating forward or backwards at the cost of an increase in memory..
| Reporter | ||
Comment 4•3 years ago
|
||
may be fruitful to see why this BFCache didnt work in 10% of instances (i.e. closed TabA/ProcessB immediately on navigating Back to TabA/ProcessA)
| Reporter | ||
Comment 5•3 years ago
•
|
||
(In reply to Mayank Bansal from comment #4)
may be fruitful to see why this BFCache didnt work in 10% of instances (i.e. closed TabA/ProcessB immediately on navigating Back to TabA/ProcessA)
On further testing, it looks like if another tab (TabC) is already open when you create TabA/ProcessA, then the "hidden process TabA/ProcessB" will close immediately on navigating back.
So STR:
- Open google.com in a new tab ("TabC")
- Perform the steps in comment #0
AR: TabA/ProcessB is immediately closed.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Description
•