Summary: | REGRESSION (r260932): ASSERTION FAILED: ok in webkit::SandboxExtension::consumePermanently for 3 tests | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Truitt Savell <tsavell> | ||||
Component: | WebKit2 | Assignee: | Brent Fulgham <bfulgham> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | bfulgham, pvollan, webkit-bot-watchers-bugzilla, webkit-bug-importer | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=211103 | ||||||
Attachments: |
|
Description
Truitt Savell
2020-04-30 14:16:42 PDT
This test uncovered a bug in our handling of Sandbox extensions that only occurs with our test infrastructure. The TestWebKitAPI (and WKTR) processes are not sandboxed, and it is possible that WebKit clients might themselves be unsandboxed. When WebKit code linked into an unsandboxed process attempts to consume a sandbox extension, we get a null handle and no error code. We should treat this as a valid and expected result. I.e., we attempted to consume a valid sandbox extension supplied by a sandboxed helper process, and the Sandbox framework says "I didn't do anything since you are not sandboxed." Created attachment 398113 [details]
Patch
Comment on attachment 398113 [details]
Patch
R=me.
Committed r260974: <https://trac.webkit.org/changeset/260974> All reviewed patches have been landed. Closing bug and clearing flags on attachment 398113 [details]. |