Unable to reproduce the issue on Win-7 and Win-10 using chrome stable version #58.0.3029.110.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Started chrome with the argument "--process-per-tab".
2. Loaded websites on different domains in the same tab i.e wikipedia.org, amazon.in and yahoo.com.
3. Observed that all the websites loaded in the same tab without any issues.

merceyz97@ - Could you please verify the screen cast and please let us know if anything missed from our side.
Also please check this issue on latest stable #58.0.3029.110 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 719961.mp4 1.6 MB

	719961.mp4 1.6 MB View Download

You'll need to watch the renderer processes in task manager

For each navigation to a new domain you'll see that one renderer closes and a new one spawns which is the default and correct.

With the "--process-per-tab" argument it shouldn't recreate the renderer, instead reuse the same one over and over again as per https://www.chromium.org/developers/design-documents/process-models

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Unable to reproduce the issue on windows 7 using chrome version 58.0.3029.110 with the below steps

1. Started chrome with the argument "--process-per-tab".
2. Opened task manager to observe the renderer process.
3. Opened yahoo.com in one tab and opened again cnn.com on the same tab
4. Every time the renderer changed to new one 

Please find the attached screen cast and confirm if anything missed here.
Observed the same behaviour on M57 as well.

Thanks,

If you observe it in the windows task manager (ctrl + shift + escape) you'll noticed it changes renderer process which it shouldn't with that argument

In your video you can also see the PID changes

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I can also confirm that it is happening in version: 60.0.3112.90

krajshree@chromium.org, did you see the last message by Mercey? I think the Status on this one should be switched from Unconfirmed, since we seem to have a clear way to reproduce it. Please let me know if you disagree.

It affects e.g. JS bindings in CEF-based frameworks like CefSharp, since the fact that the renderer process is suddenly replaced makes it much harder to persist JS bindings in a given browser window/tab.

See also https://bugs.chromium.org/p/chromium/issues/detail?id=717459

Issue is still reproducible   
https://bugs.chromium.org/p/chromium/issues/detail?id=793235

 Issue 793235  has been merged into this issue.

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot