为何多数多进程应用（如chrome.exe）共享相同进程名而非区分父子进程？

Great question—this is a common point of curiosity for anyone who’s ever stared at Task Manager and wondered why all those Chrome processes have identical names. Let’s break down the reasoning, including the points you brought up and a few more nuanced details:

Why Not Split into Parent/Child Executables? #

First, let’s address the "why separate names aren’t used" angle:

• Deployment and maintenance chaos: Splitting into multiple executables (like chrome-window.exe and chrome-tab.exe) would turn updates, installs, and version sync into a nightmare. Imagine having to ensure 5+ different EXEs are all the same version every time you push an update—one mismatched file could break the entire app. A single executable simplifies packaging, distribution, and troubleshooting.
• Unnecessary complexity: Most of these apps already distinguish process roles internally via command-line arguments (e.g., Chrome uses --type=renderer for tab processes, --type=gpu-process for GPU handling). You can see these in Task Manager’s "Command Line" column—no need for separate EXEs to tell them apart.

Advantages of Sharing a Single Executable (Beyond Deployment) #

You hit on some key points, let’s expand on them:

• Memory efficiency via Copy-on-Write (CoW): Operating systems use CoW to share read-only memory pages (like the app’s code, static assets, and libraries) across all instances of the same executable. Only when a process needs to modify a page (e.g., write to a data segment) does the system copy that page for the process alone. This drastically cuts down on memory usage—if you have 10 Chrome tabs, you’re not loading the entire Chrome codebase 10 times.
• Simplified Inter-Process Communication (IPC): When all processes run the same executable, they share the same data structures, protocol definitions, and memory mapping conventions. This means IPC between parent and child processes is faster and less error-prone—no need to handle version mismatches between different EXEs or negotiate different communication rules.
• Consistent UAC and security boundaries: Using a single executable ensures all processes inherit the same permission context. If you split into separate EXEs, launching a child process might trigger an unexpected UAC prompt (if the child needs elevated rights) or create security gaps if permissions aren’t properly aligned. For sandboxed processes (like Chrome’s tab sandbox), a single executable makes it easier for the OS to enforce uniform sandbox policies.
• Faster process startup: The OS caches file data and memory pages for recently used executables. When launching a new process from the same EXE, it can reuse these cached resources, making startup nearly instant. This is why opening a new Chrome tab feels so quick compared to launching a completely separate app.
• Easier debugging and development: For developers, maintaining one executable means less overhead—no switching between multiple project files, unified logging, and simpler performance profiling. Tools that track process behavior can target all instances of chrome.exe without needing to filter for different EXE names.

内容的提问来源于stack exchange，提问作者Michal Ciechan