Inconsistent Extension Behavior on Google Chrome Installs -
i have observed inconsistent behavior using web developer extension (chris pederick) in google chrome on these different machines:
- my pc running windows 7 home premium 64-bit
- a virturalbox virtual machine (vm) running ubuntu 12 on pc
- a vm running updated, fresh install of windows 7 home premium 64-bit on pc
i have same version of google chrome , web developer installed on these machines. however, reason, web developer not work expected on pc. works on ubuntu vm , windows vm.
on pc, 95% of time custom tools functions (validate css, validate html, etc.) in web developer nothing when clicked (they should open new tabs w3c validators).
i have uninstalled , reinstalled google chrome on pc several times. have manually gone through file system , registry remove traces of google chrome before reinstalling. nothing i've attempted far has corrected problem.
of course, due google's 'field trials', these machines have different variations (as reported chrome://version), doubt source of problem.
any ideas or suggestions?
ok, here's possible clue...
it has baffled me why problem never occurs in virtual machine (vm); on host. same version of os, chrome, , web developer installed on both. may have discovered why.
my standard settings vms use 1 cpu. test, changed vm use 2 cpus. boom! can reproduce problem on vm. change 1 cpu - can not reproduce problem.
does suggest problem threading in chrome?
Comments
Post a Comment