Description of problem: If Horizon vnc console is opened in chrome or opera, it responds very slowly. Firefox works ok. Version-Release number of selected component (if applicable): python-django-horizon-2015.1.2-4.el7ost.noarch google-chrome-stable-51.0.2704.103-1.x86_64 How reproducible: Steps to Reproduce: 1.Project->Instances->Console 2. 3. Actual results: console responds slowly in chrome and opera Expected results: console respond time in chrome is normal Additional info:
Console is handled by novnc, Horizon just forwards the connection. Please report the version of novnc being used.
Hi, the issue is hits in both versions: OSP7: openstack-nova-novncproxy-2015.1.3-7.el7ost.noarch OSP8: openstack-nova-novncproxy-12.0.2-5.el7ost.noarch novnc-0.5.1-2.el7ost.noarch
Chrome works fine up till version google-chrome-stable-50.0.2661.102-1.x86_64.rpm, once upgraded to version google-chrome-stable-51.0.2704.63-1.x86_64.rpm vnc console began to respond slowly. Ondrej
Opera behaves similarly, working: opera-stable_37.0.2178.54_amd64.rpm slowed: opera-stable_38.0.2220.29_amd64.rpm
Hi all, We need information on this bug to set the customer expectations. Please provide us the information required by Jan: 1) where the issue really is 2) is the patch available (upstream / downstream) 3) Can we fix it ? 4) When can the fix be delivered? Thank you very much, Julia
I am running some tests with latest noVNC on Red Hat OpenStack Platform and can confirm that the issue is affecting noVNC. After swapping the noVNC files shipped with upstream code we couldn't reproduce the issue. We need to identify which patch fixes the Google Chrome slowness and backport it.
Seconded. That's what I found. I even identified a patch, but there was so much refactoring, that I don't believe it's worth the effort to backport rather than to rebase to a later version. See: https://github.com/kanaka/noVNC/releases/tag/v0.6.0
Morning, could give us an update please.
Verified ======== novnc-0.6.1-1.el7ost.noarch chrome 51.0.2704.106 (64-bit)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1622.html