723e9076fe
The Linux localtime_r() can't execute in sandboxed processes so it is proxied back to the browser. There are GPU hang crash reports that happen to be in ProxyLocaltimeCallToBrowser(). Add a UMA histogram to get an idea how long this proxy call takes in the wild. It's possible the GPU watchdog is just killing a slow, instead of hung, GPU process and it happens to be in this function when the watchdog fires. Bug: 1077735 Change-Id: I0242af86244d3eaaf9dbfdebe1487ff38664d10d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2956311 Reviewed-by: Chris Thompson <cthomp@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#892191}
Sandbox Library
This directory contains platform-specific sandboxing libraries. Sandboxing is a technique that can improve the security of an application by separating untrustworthy code (or code that handles untrustworthy data) and restricting its privileges and capabilities.
Each platform relies on the operating system's process primitive to isolate code into distinct security principals, and platform-specific technologies are used to implement the privilege reduction. At a high-level:
mac/uses the Seatbelt sandbox. See the detailed design for more.linux/uses namespaces and Seccomp-BPF. See the detailed design for more.win/uses a combination of restricted tokens, distinct job objects, alternate desktops, and integrity levels. See the detailed design for more.
Built on top of the low-level sandboxing library is the
//sandbox/policy component, which provides concrete
policies and helper utilities for sandboxing specific Chromium processes and
services. The core sandbox library cannot depend on the policy component.