Changes between Initial Version and Version 1 of Ticket #12279, comment 7
- Timestamp:
- Jan 8, 2014 1:06:25 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12279, comment 7
initial v1 1 1 I like to share my latest try 2 2 3 1for the clean xp sp3 installation (I install it fresh again), not able to do a windows update, the update redirect to help page of microsoft3 1. for the clean xp sp3 installation (I install it fresh again), not able to do a windows update, the update redirect to help page of microsoft 4 4 5 2on the xp sp3 guest os, if run on GUI (thr VB interface, not headless), the VBoxService.exe use constant RAMs, however, every a few seconds, VBoxTray.exe eat 4KiB rams (hope somebody can replicate this, I upgrade VB to 4.3.2 and the addition to guest xp also 4.3.2)5 2. on the xp sp3 guest os, if run on GUI (thr VB interface, not headless), the VBoxService.exe use constant RAMs, however, every a few seconds, VBoxTray.exe eat 4KiB rams (hope somebody can replicate this, I upgrade VB to 4.3.2 and the addition to guest xp also 4.3.2) 6 6 7 3for the headless mode, I completely remove the additions. Then there is no problem of VBoxService.exe and VBoxTray.exe . Since I only access them by remote desktop, the ADDITION doest not give any help, but ask me to restart the vm every week, otherwise, they eat up the RAM and the VMs hang up. The memory leak have been lating for more than 15 months, now I am free of this leaking by remove the addition on the headless VMs.7 3. for the headless mode, I completely remove the additions. Then there is no problem of VBoxService.exe and VBoxTray.exe . Since I only access them by remote desktop, the ADDITION doest not give any help, but ask me to restart the vm every week, otherwise, they eat up the RAM and the VMs hang up. The memory leak have been lating for more than 15 months, now I am free of this leaking by remove the addition on the headless VMs.
