New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e10s: user scripts fail to load due to the content process sandbox #2485
Comments
Thank you immensely for your careful and detailed report! With WebExtensions looming, most of my available time has been looking there, so that Greasemonkey could survive the year. If you finish the above work into a pull request, it's likely to be merged. If not, I can't promise when/if I can do that myself. |
AFAIK: It's not so easy... See #2376 |
@arantius Would it be OK to fix only the script stuff for now and leave |
Absolutely. Partially working is better than not working at all. |
this seems to be a dup of #2296 |
WFM as is on Windows, so this error must be Mac only (as hinted at in the original description). Fix verification will be tricky for me as Mac is not a primary (and definitely not a development) platform. |
I've just pushed version 3.11beta1: https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/versions/beta?page=1#version-3.11beta1 It would be very useful if you could install it and confirm that it fixes this issue. |
This problem has returned: |
Firefox gradually introduces/introduced a sandbox for content processes[1]
Said sandbox will all block file accesses[2] when the level is configured to be at least 2, which is the case for Nightly at the moment. The sandbox works at least on macOS, meaning user scripts fail to load when e10s is enabled.
STR
console.log("hello, world");
)Expected:
User script runs
Actual:
User script fails to run with the subscript loader bailing with
Console.app
where sandbox violations are logged in macOSWorkarounds
security.sandbox.content.level
to1
or0
lowering the sandbox protectionsRemedies
Sync-message the main process and have it load the script source, then
evalInSandbox
the contents.I prodded the source a bit till it seemed to work. Also
@resource
is not addressed at all but would work similarly I guess. Due to these caveats, no pull request.[1] https://wiki.mozilla.org/Security/Sandbox
[2] https://wiki.mozilla.org/Sandbox/OS_X_Rule_Set#How_security.sandbox.content.level_Affects_File_Access
The text was updated successfully, but these errors were encountered: