This experiment/feature breaks Slack, I appear to be on the "freeze after 10 minutes" experiment, and after a Slack tab is frozen it shows as disconnected in the favicon and status and notifications are not delivered until the tab is unfrozen.
I've also filed support ticket 1804414 with Slack and pointed at this issue.
For any future re-lands of these patches – after tracking down and fixing the cause of the above assertion failure – please add the following line to the CL description to run these additional tests:
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Thanks.
My corp machine is in the ProactiveTabFreezeAndDiscard-FreezeAndDiscardHighTabCountOnlyAggressive9_Dogfood group. I have to say, this is *really really* irritating. I have a number of crbug.com tabs and code review tabs open that I go back to throughout the day, and every single one needs to be reloaded when I go back to it. I'm on the verge of manually overriding the experiment using disable-features.
That might suggest the heuristics that a tab is unlikely to be used again aren't all that accurate....
Could you share the content of chrome:://discards ? Feel free to remove the URLs if you don't want to share them. This is really not the expected behavior.
My chrome://discards is attached. I'm on Mac OS X Dev 70.0.3538.9 and there are 77 tabs all up in discards (I'm not sure if that's high or low or when it's refreshed). If this is only during the current session of Chrome, I restarted my browser this morning and it's been up for about 9 hours so far.
Thanks for the data! It looks like all the discarded tabs haven't been used for more than 8 hours, which shouldn't cause any reload during the same day? (the time here is relative to the active usage time of Chrome, the timer stop when you stop using Chrome for more than 5 minutes).
Could it be a session restore issue? E.g. some tabs not being loaded when you restart Chrome and so they to be loaded the first time you navigate to them.
Note that we will soon stop the discarding experiments and only enable tab freezing, if the current feature is too painful then I'd recommend switching chrome://flags/#proactive-tab-freeze-and-discard to "Enabled Freeze only" (AFAWK there's no negative side effects associated with tab freezing and this has a clear performance impact).
Thanks
