-
This Tweet is unavailable.
-
There are some sites with like 100 iframes.
2 replies 0 retweets 3 likes -
Replying to @pcwalton @BRIAN_____ and
OOPIFs mean (as in Gazelle) all the iframes from same origin might share a process. That helps in practice. Rare to have near 100 origins.
2 replies 1 retweet 0 likes -
Replying to @BrendanEich @BRIAN_____ and
It’s rare, but do you break sites that do it? Because if you don’t, malicious sites can trigger that condition, hurting the security benefit
1 reply 0 retweets 1 like -
Replying to @pcwalton @BRIAN_____ and
Sites can always OOM. Unloads bgtabs.
1 reply 0 retweets 0 likes -
Any reasonable “hit the too-many-origins” limit will be way lower than the OOM threshold.
2 replies 0 retweets 0 likes -
As
@nasko pointed out, OOPIF means one process per origin, so you won't OOM until lots of iframe origins in force-loaded abs. Should be ok.2 replies 0 retweets 0 likes -
Let me restate. The problem is that sites that don’t OOM *today* would *start* to OOM.
1 reply 0 retweets 0 likes -
Replying to @pcwalton @BrendanEich and
Which is why *even Google Chrome* is not going to put all origins in separate processes.
1 reply 0 retweets 1 like
For some reason, you all think I’m pushing back against what Chrome is doing. I’m not! I think they’re doing the right thing.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.