Changes between Version 1 and Version 2 of Ticket #15478, comment 7
- Timestamp:
- Feb 20, 2018 11:24:06 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15478, comment 7
v1 v2 5 5 When VBoxTray.exe has high CPU load then the Windows-Client becomes almost completely unresponsive, because of long delays - killing VBoxTray.exe is very hard to achieve then. I see that problem on my Windows 7 32 Bit Client at least every second day, often even multiple times per day. 6 6 7 Maybe it is important to note, that i **disabled graphics-acceleration (2D and 3D)** for the client because of problems (at least in past) with **multiple GPU's** (AMD and Intel) and usage of **multiple monitors on Host**, as this seems not to be a usual case. I also **enabled the bidirectional cli bboard** what also seems not to be the default.7 Maybe it is important to note, that i **disabled graphics-acceleration (2D and 3D)** for the client because of problems (at least in past) with **multiple GPU's** (AMD and Intel) and usage of **multiple monitors on Host**, as this seems not to be a usual case. I also **enabled the bidirectional clipboard** what also seems not to be the default. 8 8 9 9 This problem should have highest priority of all actual problems, because "using a client" should be the main-goal of VirtualBox in my opinion. 10 11 EDIT: Even with disabled clipboard-exchange the problem happens.