There are portions of the codebase that use the contentWindowAsCPOW and contentDocumentAsCPOW properties on a <xul:browser> (remote or not). We should examine each point we use one of these properties, and see what happens to the CPOW - tracing whether or not we store them, and figuring out how much traffic goes across them during their lifetime. If we can identify some bad offenders, we should then find a way of not using CPOWs for those cases. : These properties are explicitly CPOWs in the remote browser case
tracking-e10s: --- → ?
tracking-e10s: ? → +
tracking-e10s: + → ?
You need to log in before you can comment on or make changes to this bug.