test_iframe_sandbox_general.html fails with Windows content sandbox

RESOLVED FIXED in mozilla35

Status

()

defect
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: bobowen, Assigned: bobowen)

Tracking

unspecified
mozilla35
All
Windows 7
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

Assignee

Description

5 years ago
content/html/content/test/test_iframe_sandbox_general.html fails with the Windows content sandbox enabled.

Adding the L"\\??\\pipe\\chrome.*" file system rule (the same as the GMP process one) seems to fix this.
Assignee

Comment 1

5 years ago
I think this is a fairly uncontroversial addition.
Attachment #8490066 - Flags: review?(tabraldes)
Assignee

Comment 2

5 years ago
Let's try that again with the actual code change included. :-)
Attachment #8490066 - Attachment is obsolete: true
Attachment #8490066 - Flags: review?(tabraldes)
Attachment #8490068 - Flags: review?(tabraldes)
Attachment #8490068 - Flags: review?(tabraldes) → review+
Assignee

Comment 4

5 years ago
This is part of the set-up of the sandboxed process, so will only run when the Windows content sandbox is enabled. This doesn't happen by default at the moment.

Here's a try run showing that this change means that test_iframe_sandbox_general.html works:
https://tbpl.mozilla.org/?tree=Try&rev=c0de59972f34
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/b1280bbd4a03
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
You need to log in before you can comment on or make changes to this bug.