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
chore: re-enable devtools renderer sandbox #16864
Conversation
dad8bf8
to
8beae03
Compare
The tests for MAS builds are failing due to the devtools renderer crashing with this call stack:
@nornagon, @zcbenz do you have any idea why this could be happening? The non-MAS builds are working fine. |
|
@nornagon I've checked the changes in
when that happens, I can see that |
ff3f490
to
4ba455f
Compare
4ba455f
to
dcb75d5
Compare
Release Notes Persisted
|
Description of Change
/cc @nornagon, @deepak1556
Checklist
npm test
passesRelease Notes
Notes: Enabled sandboxing of devtools and chrome extension background script host renderers.