To do this, we'll need everything to run in the parent process. That means that the content policy stuff will have to be moved to an http-on-modify handler or something.
making major as needed for ghostery - 15M users
make that 1.5M users - still major impact
This is being fixed by the patch I've just attached to bug 1163862. Should I resolve this one as a dupe?