RestrictCoreSharingOnRenderer

Restrict CPU core sharing for renderer process

Supported on:

  • Chrome (Windows) since version 140

Description:

This policy mitigates side-channel cross process memory attacks by isolating the renderer process on the CPU core and preventing other processes from sharing the same core. The mitigation is supported on Microsoft® Windows® 11 24H2 and above. If the OS does not have the required scheduling support, this policy will have no effect. This policy may slow down performance in some demanding scenarios similar to disabling hyperthreading. For more information refer https://learn.microsoft.com/en-us/windows/win32/api/winnt/ns-winnt-process_mitigation_side_channel_isolation_policy
If this policy is enabled, all other processes will not be scheduled on the same CPU core when the renderer process is running.
If this policy is disabled, all other processes can be scheduled on the same CPU core if a renderer process is running on it.
If this policy is not set, all other processes can be scheduled on the same CPU core if a renderer process is running on the core. This may vary depending on Samsung Browser release, currently running field trials, and platform.

true = All other processes will not scheduled on the same CPU core when renderer process is running on it.
false = All other processes can be scheduled on the same CPU core when renderer process is running on it.
not set = Allow the user to decide

Supported features:

  • Applied to browser only after restart.
  • Applied at Samsung Browser level, cannot be set by Cloud user policies.

Data type:

Boolean
Windows:REG_DWORD

Windows registry location:

Software\Policies\Samsung\Internet\RestrictCoreSharingOnRenderer

Example value:

0x00000001

More policies under Miscellaneous: