Go to the Details tab in the Task Manager > right-click on one of the columns > Select columns > add command-line. You can then see the command-line parameters for each process. Don't expect to understand these entirely. If you need further details why the respective apps need to create additional processes beyond "code-isolation", then you will need to refer the 3rd party developer documentation/forums for specific details, e.g. https://community.spotify.com/t5/Desktop-Window...
Excessive Duplicate Processes
Noticed a few days ago, seeing an excessive amount of duplicates of several programs I use in task manager under details. Like 7 copies of steam, 6 of spotify, 8 of firefox when i only have 4 tabs open, etc. any thoughts?
Also i dont think i should have literally 60+ iterations of svhost running
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
3 answers
Sort by: Most helpful
-
Anonymous
2020-10-26T01:34:33+00:00 -
Anonymous
2020-10-26T01:28:49+00:00 That doesnt quite explain why double or more then what should be there even by number of tabs. when only 4 tabs open and no other browser open i should only be running at most maybe 5 processes. I have 10 right now and its not isolated to just browsers. There are excess duplicates of almost every program running that I as the user would launch. Currently running avast to see if it can find anything that could be causing it just trying to cover bases ahead of time
-
Anonymous
2020-10-26T01:08:44+00:00 Hi and thanks for reaching out. My name is William. I'm a Microsoft Windows Certified Professional and Systems Administrator. I'll be happy to help you out today.
This is by design. All modern browsers (Chrome, Edge, Firefox) isolate various extensions/add-ons in separate tabs so that code for a the respective components do not crash the host (parent) process. Spotify does something similar by isolating the crashpad, the debug log and some other minor code in different child processes.