![Dave Tapuska](https://web.dev/images/authors/dtapuska.jpg) Dave Tapuska [X](https://twitter.com/dtapuska) [GitHub](https://github.com/dtapuska) ![Jecelyn Yeen](https://web.dev/images/authors/jecelynyeen.jpg) Jecelyn Yeen [X](https://twitter.com/jecfish) [GitHub](https://github.com/jecfish) [Bluesky](https://bsky.app/profile/jec.fish) [Homepage](https://jec.fish/)

<br />

If you see a message stating "This tab shares resources with other tabs..." infobar while DevTools is open, then you are part of the small group with the **Process sharing** experiment enabled. This post explains the experiment.
![](https://developer.chrome.com/blog/image/1-process-sharing-infobar.jpg) The "This tab shares resources with other tabs, which could interfere with debugging." infobar.

## What's the experiment about?

Normally, when you open multiple tabs from the same website (like [Google Docs](https://google.com/docs)), Chrome creates a separate renderer process for each. The **Process sharing** experiment changes this by allowing multiple tabs to share the same renderer process.

The goal is to improve performance. For example, faster page loads, improved ([LCP](https://web.dev/articles/lcp)), and lower memory use. You can learn more in this [detailed document](https://docs.google.com/document/d/1Z7qYfU9QI-IJOXvkNc4RPlKZ1sUoZz1yOHu-ClqvxtI).

## How does this affect developer experience in Chrome DevTools?

Since tabs might share a process (and its main thread), there are two impacts on debugging and performance analysis:

**Breakpoint debugging** . If you pause the debugger in one tab, it can affect others sharing the process. You'll see the "Debugger paused in another tab, click to switch to that tab." warning.
**Performance analysis**. Heap snapshots and performance recordings might capture data from multiple tabs, making results harder to interpret.
![](https://developer.chrome.com/blog/image/2-debugger-paused-warning.jpg) The "Debugger paused in another tab, click to switch to that tab." warning.

## Opting in or out of the experiment

### Who's opted out by default

This experiment is turned off by default for the following users:

- [Chrome Enterprise](https://chromeenterprise.google/) users
- [Chrome For Testing](https://developer.chrome.com/blog/chrome-for-testing)
- [Chrome Headless](https://developer.chrome.com/docs/chromium/headless)
- Developers who've used DevTools recently (in the past seven days)

### Opting out

You can manually opt out by clicking the **Opt Out** button in the warning. Or, disable the **Enable ProcessPerSite up to main frame threshold** experiment using **Chrome flags settings** (`chrome://flags/#enable-process-per-site-up-to-main-frame-threshold`).
![](https://developer.chrome.com/blog/image/3-opt-out-button.jpg) The Opt out button in the Process sharing infobar.

### Opting In

To explicitly test the new experiment feature, launch Chrome with the following [command line flags](https://developer.chrome.com/docs/web-platform/chrome-flags):

    --enable-features=ProcessPerSiteUpToMainFrameThreshold:ProcessPerSiteMainFrameThreshold/20 -disable-features=ProcessPerSiteSkipDevtoolsUsers,ProcessPerSiteSkipEnterpriseUsers

## Feedback

We'd love to hear your feedback on the **Process sharing** experiment! Share your questions or any issues you encounter in this [feedback tracker](https://crbug.com/366284857).

## Download the preview channels

Consider using the Chrome [Canary](https://www.google.com/chrome/canary/), [Dev](https://www.google.com/chrome/dev/), or [Beta](https://www.google.com/chrome/beta/) as your default development browser. These preview channels give you access to the latest DevTools features, let you test cutting-edge web platform APIs, and help you find issues on your site before your users do!

## Get in touch with the Chrome DevTools team

Use the following options to discuss the new features, updates, or anything else related to DevTools.

- Submit feedback and feature requests to us at [crbug.com](https://crbug.com).
- Report a DevTools issue using the **More options** \> **Help** \> **Report a DevTools issue** in DevTools.
- Tweet at [@ChromeDevTools](https://twitter.com/intent/tweet?text=@ChromeDevTools).
- Leave comments on [What's new in DevTools YouTube videos](https://goo.gle/devtools-youtube) or [DevTools Tips YouTube videos](https://goo.gle/devtools-tips).