caesar7
New Member
- Joined
- Aug 9, 2021
- Messages
- 1
- Thread Author
-
- #1
Whenever an instance of BlueStacks is opened for the first time, it launches a Bluestacks.exe* that looks like it 'handles' all other futures instances opened:
It then launches BlueStacks.exe and HD-Player.exe for each new instance, where each of them is dependent on each other, if you close one the other is also closed.
When I have multiple instances running at the same time I can't figure out what HD-Player.exe belongs to what BlueStacks.exe, when i try to get the parent PID of any of these executables it always points to the PID of the first BlueStacks.exe* opened:
(http://imgur.com/fzxqSyN)
As seen in the image HD-Player points as parent the process with PID 13028 (the first Bluestacks launched), and 13028 points to the multi-instance manager who launches the processes, also If you close the first Bluestacks.exe* everything is closed.
Why do I need to know it?
Is the HD-Player who opens and uses the ports to connect with the android debug (adb).
Then when I need to use the port for a specific instance, I don't know what PID to use to listen to the port as i don't know the HD-Player responsible for it.
Would like to ask for ideas on how I could figure what Player belongs to what BlueStacks.
It then launches BlueStacks.exe and HD-Player.exe for each new instance, where each of them is dependent on each other, if you close one the other is also closed.
When I have multiple instances running at the same time I can't figure out what HD-Player.exe belongs to what BlueStacks.exe, when i try to get the parent PID of any of these executables it always points to the PID of the first BlueStacks.exe* opened:
As seen in the image HD-Player points as parent the process with PID 13028 (the first Bluestacks launched), and 13028 points to the multi-instance manager who launches the processes, also If you close the first Bluestacks.exe* everything is closed.
Why do I need to know it?
Is the HD-Player who opens and uses the ports to connect with the android debug (adb).
Then when I need to use the port for a specific instance, I don't know what PID to use to listen to the port as i don't know the HD-Player responsible for it.
Would like to ask for ideas on how I could figure what Player belongs to what BlueStacks.
Solution
To identify which HD-Player process corresponds to a specific BlueStacks instance, you can utilize certain tools and approaches:
1. Resource Monitor:
- Network Tab: Use the Resource Monitor while Bluestacks is running.
- Open Resource Monitor (press
Win + R, typeresmon, and hit Enter). - In the Network tab, you can see which processes are utilizing network resources.
- Look for HD-Player.exe processes associated with each Bluestacks instance.
2. Command Line:
- Open Command Prompt.
- Run
tasklist > tasks.txtto save the running processes to a text file. - Analyze this file to identify...
- Open Resource Monitor (press
- Joined
- Mar 14, 2023
- Messages
- 100,308
To identify which HD-Player process corresponds to a specific BlueStacks instance, you can utilize certain tools and approaches:
1. Resource Monitor:
- Network Tab: Use the Resource Monitor while Bluestacks is running.
- Open Resource Monitor (press
Win + R, typeresmon, and hit Enter). - In the Network tab, you can see which processes are utilizing network resources.
- Look for HD-Player.exe processes associated with each Bluestacks instance.
2. Command Line:
- Open Resource Monitor (press
- Use a port monitoring tool to track which processes are using specific ports.
- Tools like TCPView can help you determine which HD-Player process is associated with a particular port.
Summary:
By combining the information available in the Resource Monitor, Command Line outputs, tools like Process Explorer, and port monitoring utilities, you should be able to track down which HD-Player process corresponds to each individual BlueStacks instance. This method will provide more visibility into the processes and their relationships, allowing you to manage ports effectively for each instance.
- Tools like TCPView can help you determine which HD-Player process is associated with a particular port.