RESOLVED FIXED 195379
[macOS] Sandbox call violation causes WebContent process to crash
https://bugs.webkit.org/show_bug.cgi?id=195379
Summary [macOS] Sandbox call violation causes WebContent process to crash
Per Arne Vollan
Reported 2019-03-06 14:29:26 PST
A new call needs to be added to the allow list in the WebContent process' sandbox.
Attachments
Patch (1.20 KB, patch)
2019-03-06 14:31 PST, Per Arne Vollan
bfulgham: review+
Patch (1.28 KB, patch)
2019-03-06 14:40 PST, Per Arne Vollan
no flags
Per Arne Vollan
Comment 1 2019-03-06 14:29:50 PST
Per Arne Vollan
Comment 2 2019-03-06 14:31:34 PST
Brent Fulgham
Comment 3 2019-03-06 14:33:40 PST
Comment on attachment 363794 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=363794&action=review > Source/WebKit/WebProcess/com.apple.WebProcess.sb.in:972 > + (syscall-number SYS_memorystatus_control) I suggest you add a comment with the Radar#, or perhaps the reason we need to include this (e.g., list which Framework uses it.) I this case, I think it night be: "..._control) ;; Needed for memory measurement infrastructure" Or something like that.
Per Arne Vollan
Comment 4 2019-03-06 14:40:57 PST
Per Arne Vollan
Comment 5 2019-03-06 14:42:13 PST
(In reply to Brent Fulgham from comment #3) > Comment on attachment 363794 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=363794&action=review > > > Source/WebKit/WebProcess/com.apple.WebProcess.sb.in:972 > > + (syscall-number SYS_memorystatus_control) > > I suggest you add a comment with the Radar#, or perhaps the reason we need > to include this (e.g., list which Framework uses it.) > > I this case, I think it night be: > > "..._control) ;; Needed for memory measurement infrastructure" > > Or something like that. Thanks for reviewing! I have updated the patch.
WebKit Commit Bot
Comment 6 2019-03-06 15:08:37 PST
Comment on attachment 363795 [details] Patch Clearing flags on attachment: 363795 Committed r242570: <https://trac.webkit.org/changeset/242570>
Note You need to log in before you can comment on or make changes to this bug.