Bug 1134284 accesses the safebrowsing database from a content loader, which doesn't work in e10s since the safebrowsing API can only be called from the parent.

Hey Monica, the e10s team tried to triage this today but we weren't sure what to do with it. Is this an e10s blocker or is it unrelated?

Doesn't this depend on jsplugins work anyway?

In reply to Benjamin Smedberg [:bsmedberg] from comment #2) > Doesn't this depend on jsplugins work anyway? Yes, bug 1134284 depends on jsplugins. I don't think this is an e10s blocker. My impression is that Josh wanted to resolve bug 1134284 a different way (by replacing all of Flash with Shumway?) before e10s is scheduled to launch anyway. I just filed this bug to make sure that someone knew it wasn't compatible with e10s. Redirecting to Josh to make sure that's right.

thanks. not blocking e10s rollout at this time, tracking so we don't forget about it.

We want to switch Flash ads to Shumway before e10s is ready, and eventually we want that to work with e10s. The issue here has nothing to do with js plugins, really. The issue is that we make a decision about whether something is an ad or not in ObjectLoadingContent, in the DOM. This code runs in a content process under e10s, and thus it can't query the TP database (or whatever database we end up using, presumably), because that is only available in the chrome process. I've talked to bz about this a bit over email.

(In reply to Josh Aas (Mozilla Corporation) from comment #5) > We want to switch Flash ads to Shumway before e10s is ready, and eventually > we want that to work with e10s. Ok, thanks. Tracking on this, dumping in the post aurora uplift bin.

Andrew, can you please verify this bug has been fixed after you fix (shavar whitelist check) bug 1134284?