Web Browser Launch - starts multiple instances

[Trevor Chandler]

Hello CINners,



When I launch one of my web browsers (Edge, Chrome, Firefox), there's always
multiple browser processes that are running - even though I only have one tab
open on the web browser. Why do I see these multiple browser processes in
Task Manager, when I only have a single tab open in my browser? I've never
understood this - and I don't recall ever being educated on this. I did say I don't
recall

I promise, I have ONLY one tab open!!!!

Thanks CINners!

 

[Rick Butler]

Microsoft Edge is considered to be a multi-threaded, modern browser, so it's going to split up processes for better performance. You'll see the same thing with Chrome, since Edge is based on the Chromium engine. If it were only one process, you'd only be able to run it on one processor core. Since we know that most processors are multi-core, splitting the browsing experience across multiple cores greatly enhances the experience.

 

[precious]

Edge, Chrome, and Firefox use a multi-process architecture for security and performance. Each tab, extension, and sometimes even parts of the browser’s UI run in separate processes.

How web browsers use Processes and Threads

 

[Trevor Chandler]

Microsoft Edge is considered to be a multi-threaded, modern browser, so it's going to split up processes for better performance. You'll see the same thing with Chrome, since Edge is based on the Chromium engine. If it were only one process, you'd only be able to run it on one processor core. Since we know that most processors are multi-core, splitting the browsing experience across multiple cores greatly enhances the experience.

I'm so glad that you mentioned that I'd see the same thing with Chrome - cause I certainly do!!! Not only with Chrome, but Firefox as well.

Okay, so I can relax now. I was thinking that maybe something nefarious was taking place behind the scenes.

Many thanks Mr. Rick Butler!!!

 

[Trevor Chandler]

Edge, Chrome, and Firefox use a multi-process architecture for security and performance. Each tab, extension, and sometimes even parts of the browser’s UI run in separate processes.

How web browsers use Processes and Threads

precious, you're an all-in-one Help Desk!!!

Thank you! Thank you!! Thank you!!!

 

[precious]

precious, you're an all-in-one Help Desk!!!

Thank you! Thank you!! Thank you!!!

Hahaha!... Thank you so much... You are the source of hot discussion here

 

[Trevor Chandler]

Hahaha!... Thank you so much... You are the source of hot discussion here

You're too kind precious!!!!

 

[precious]

You're too kind precious!!!!

Am thankful for your heart pleasing words... We'll discuss more here

 

[Rick Butler]

I'm so glad that you mentioned that I'd see the same thing with Chrome - cause I certainly do!!! Not only with Chrome, but Firefox as well.

Okay, so I can relax now. I was thinking that maybe something nefarious was taking place behind the scenes.

Many thanks Mr. Rick Butler!!!

Surely. I was a bit alarmed when I first saw that as well, and when I had an abhorrent browser which had a process that I needed to kill. Finding which one, without killing my other browsers was a challenge.

Plus, as I think about it, common elements can open in a containerized process, so each browser doesn't have to open everything for every browser instance (if that makes sense).

 

[Michael Schmitz]

I'm so glad that you mentioned that I'd see the same thing with Chrome - cause I certainly do!!! Not only with Chrome, but Firefox as well.

Okay, so I can relax now. I was thinking that maybe something nefarious was taking place behind the scenes.

Many thanks Mr. Rick Butler!!!

You did not know, that Microsoft replaced their Edge Engine years ago (Jan, 15th 2020) with Chromium?
Something that does come up in A+ to tell, or in Security courses, when talking about Browser Attacks..

 

[Trevor Chandler]

Surely. I was a bit alarmed when I first saw that as well, and when I had an abhorrent browser which had a process that I needed to kill. Finding which one, without killing my other browsers was a challenge.

Plus, as I think about it, common elements can open in a containerized process, so each browser doesn't have to open everything for every browser instance (if that makes sense).

I'm gonna have to swirl this one around in my mouth a few times to get the full affect of what you're attempting to convey here. Standby ...