Opened 9 years ago
Last modified 9 years ago
#14988 new defect
Starting 2nd instance takes too much time
| Reported by: | Edward Yang | Owned by: | |
|---|---|---|---|
| Component: | GUI | Version: | VirtualBox 5.0.12 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Windows |
Description
Starting VB for the first time usually takes only less than 1 second on my computer (Windows 10 with SSD drive). But starting the 2nd instance would always take almost 5 seconds or more. That is not normal.
BTW, this problem has been there for years since I started using VB of 3.x.
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Very hard to reply anything without more information. I would at least expect the VBox.log files of the two VM sessions you are trying to start. It might be a resource problem (CPU and/or RAM): When you start your second VM then the first VM already occupies CPU/RAM which might influence the second VM.
comment:3 by , 9 years ago
It's not related to VM sessions. I think you guys can try it yourself. Just try to launch VB GUI 2 times from Start Menu shortcut.
comment:4 by , 9 years ago
Right, if VirtualBox.exe is already running then starting the second instance of it takes ~10 seconds. Thanks.
I want to add that this happens only when there are no VMs running except the main GUI instance. Hope I made the problem clear.