Stop warmup of dbghelp.dll

dbghelp.dll is delayloaded and this code existed to verify
that it did not need warming up by enabling a feature flag.

This CL removes the warmup code and the feature. After this
CL all child processes will only load dbghelp.dll if its
functions are called.

Bug: 439521000
Change-Id: I4818c53649b5d08f0d102ccbe29f9849606e1675
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7047179
Reviewed-by: Rakina Zata Amni <[email protected]>
Commit-Queue: Alex Gough <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1557866}
NOKEYCHECK=True
GitOrigin-RevId: b1ee8d03b370005a859221fb338153849f6274c3
2 files changed
tree: d86728e046ffe4c3cd38f1c40ccdd0d8cb6cdf76
  1. linux/
  2. mac/
  3. policy/
  4. win/
  5. BUILD.gn
  6. COMMON_METADATA
  7. constants.h
  8. DEPS
  9. DIR_METADATA
  10. features.cc
  11. features.gni
  12. features.h
  13. OWNERS
  14. README.md
  15. sandbox_export.h
README.md

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.