Proactive Tab Freeze & Discard mode?

[dude99]

Under chrome://flags/#proactive-tab-freeze-and-discard there are 5 options. I would like to know what's the different between option 4 & 5 (with/without heuristics disabled).

AFAIK freeze means stopping background tab's time based js from running indefinitely; & discard is unload tab's content from memory. But I never heard anything about the heuristic thingy, & most advice on Internet are to disabled it...

So, anyone know what the heuristic really do? Is it bad for performance or privacy?

Thanks for your time & support.

[LonM]

@dude99 said in Proactive Tab Freeze & Discard mode?:

chrome://flags/#proactive-tab-freeze-and-discard

I would suspect that the "heuristics" probably look for pages that should remain active in the background - it'll be simple checks like "is this site playing audio that the user explicitly asked for" or something like that. Then it knows whether that page shouldn't be hibernated.

I would doubt that there would be any privacy implications, but I'm sure google could surprise me.

But I don't know for certain, you would get a better response from someone familiar with the chrome engine.

[dude99]

@LonM said in Proactive Tab Freeze & Discard mode?:

I would doubt that there would be any privacy implications, but I'm sure google could surprise me.

If it's about google's AI or "machine learning", then they won't be able to learn anything if no data is send back to 'em for "analysis purposes"; u know, to improve their service in order to better "serve" their consumers products. LOL

.

But I don't know for certain, you would get a better response from someone familiar with the chrome engine.

So... no answer will be found in this forum? I guess I should have waited until Monday to post this question to get better exposure from V team.

[LonM]

@dude99 If you're willing to sacrifice yourself you could try experimenting with different sites to see what happens.

Note that because this is a "flag" even the devs may not know what it does.

[dude99]

@LonM Really? So Vivaldi team didn't look at all of 'em when adopting Blink engine?

[LonM]

@dude99 Flags are frequently added and removed by the chrome engineers, they appear / disappear as experiments every time the chrome engine code is updated.

[dude99]

@LonM Oh ok. I think the heuristic thingy is pretty new, recently some people complaining about the auto discard being too aggressive . And most advise from Internet is disabled the function completely, or enabled with heuristics disabled.

I guess I better disabled it while waiting for it to "graduate" from kindergarten. LOL