Any known issue with Google Chrome?
Posted: 18. Jul 2015, 01:24
Is there any known issue with running Google Chrome on recent VBox v.4.3.x releases on Win7x64?
Have VBox v.4.3.28 running on Windows7ProSP1 x64 host, with guest VMs also running Windows7ProSP1 x64, upgraded from v.4.3.20 to resolve issue with NAT network.
On guest, have latest Chrome v.43.0.2357.134m, and only built-in IE8 installed as part of Win7x64 and no other third-party browsers.
Seems at times when Chrome is running, am periodically experiencing host HDD becoming pegged on sometimes for minutes at time causing running apps to go unresponsive. Have not been able to isolate I/O to particular process(es) but seems related to Chrome as behavior does not seem to occur when Chrome is not running nor does it seem to occur on different VBox guests that do not have Chrome installed. Am fairly confident behavior is not related to malware as full antivirus scans have always turned up nothing and am reasonably cautious with preventing malware infection. Am fairly sure behavior did not manifest with earlier VBox v.4.3.x versions.
Would VBox v.5.0 performance improvements possibly address this behavior?
Any insight would be appreciated.
Have VBox v.4.3.28 running on Windows7ProSP1 x64 host, with guest VMs also running Windows7ProSP1 x64, upgraded from v.4.3.20 to resolve issue with NAT network.
On guest, have latest Chrome v.43.0.2357.134m, and only built-in IE8 installed as part of Win7x64 and no other third-party browsers.
Seems at times when Chrome is running, am periodically experiencing host HDD becoming pegged on sometimes for minutes at time causing running apps to go unresponsive. Have not been able to isolate I/O to particular process(es) but seems related to Chrome as behavior does not seem to occur when Chrome is not running nor does it seem to occur on different VBox guests that do not have Chrome installed. Am fairly confident behavior is not related to malware as full antivirus scans have always turned up nothing and am reasonably cautious with preventing malware infection. Am fairly sure behavior did not manifest with earlier VBox v.4.3.x versions.
Would VBox v.5.0 performance improvements possibly address this behavior?
Any insight would be appreciated.