2.1.5rc1 executeSandbox change

[al_9x]

x [Surrogate] Surrogates triggered by content policy calls get executed in a sandbox

Curious, what is the reason for this? Is there still a perf issue with the sandbox?

[Giorgio Maone]

x [Surrogate] Surrogates triggered by content policy calls get executed in a sandbox

https://bugzilla.mozilla.org/show_bug.cgi?id=691242

Curious, what is the reason for this? Is there still a perf issue with the sandbox?

I assume there are more than one, but they're better than crashing on assertions and they should get better over the time because any JetPack-based add-on is much more affected than NoScript.

[al_9x]

I assume there are more than one, but they're better than crashing on assertions and they should get better over the time because any JetPack-based add-on is much more affected than NoScript.

Could you add a pref for this, for troubleshooting purposes if nothing else? If I or whoever run into a perf regression, it would be helpful to be able to quickly revert to DOM and compare.

Additionally, I have since tried to repro (per the bug) and can't with any Fx channel, I have also not experienced any consistent crashes elsewhere, so if there is a perf hit (from what I remember it was pretty bad for slower CPU's (P4, Atom), I was experiencing regular brief hangs, with just normal day to day usage with not so many tabs (20-30)), I would need to be able to stick with DOM.

[Giorgio Maone]

Could you add a pref for this, for troubleshooting purposes if nothing else?

Done in latest development build 2.1.5rc3.
Did you actually notice any performance issue so far?

[al_9x]

Could you add a pref for this, for troubleshooting purposes if nothing else?

Done in latest development build 2.1.5rc3.

Thanks. Not sure if it matters, as it appears to only affect Fx3, but 2.1.4 called executeDOM rather than execute.

Did you actually notice any performance issue so far?

Haven't tried 2.1.5 yet.