Cant render window on Ubuntu 16 in VM with 3D acceleration
Reported by
barryst...@gmail.com,
Oct 24 2016
|
|||
Issue descriptionChrome Version : 53.0.2785.143 OS Version: Ubuntu 16.04 What steps will reproduce the problem? 1. Create VM in VirtualBox (5.1.6) VM, enable 3D hardware acceleration. 2. Install Ubuntu 16.04 and install VB VM additions. 3. Install Chrome (from https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb) 4. Start chrome. (Windows 10 host (Dell Precision Tower 3620 with NVIDIA NVS 315 GPU) What is the expected result? A window with working should UI appear. What happens instead of that? A window with render issues appears; parts of other non-chrome windows are rendered in instead and the window is entirely unusable except for the Ubuntu mainmenu bar which is unaffected. I can trigger the chrome "save as" window but it has the same problem. I have attached the output of about:gpu I will attach a screenshot later. I tried testing with Chrome Canary but https://www.google.com/chrome/browser/canary.html says its not available for Linux. Workaround: Disable 3D acceleration for that VM in VB. I will attach the output of about:gpu later. -or- Start using `google-chrome --disable-gpu`. I have attached the output of about:gpu UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
,
Oct 24 2016
Thanks for making this a standalone bug! The gpu info with the problem shows that partial swaps are disabled (which might have been causing the problem). Can you run chrome with "--enable-gpu-service-logging --enable-gpu-debugging"? It will dump all the OpenGL calls made by Chrome which might help understand what the problem is without having to replicate your setup. +cc piman, do you remember a bug like that?
,
Oct 24 2016
virtualbox has driver issues - see bug 656572. I think we should blacklist it, unless someone is willing to spend the time to implement workarounds.
,
Oct 24 2016
,
Oct 25 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9154331c218d5917c7f27b9dedcc4d1cf884c7b8 commit 9154331c218d5917c7f27b9dedcc4d1cf884c7b8 Author: piman <piman@chromium.org> Date: Tue Oct 25 01:12:46 2016 Blacklist VirtualBox driver on linux BUG=656572, 658668 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2443413002 Cr-Commit-Position: refs/heads/master@{#427208} [modify] https://crrev.com/9154331c218d5917c7f27b9dedcc4d1cf884c7b8/gpu/config/software_rendering_list_json.cc
,
Oct 25 2016
This blacklist entry will fix the rendering problem.
,
Oct 25 2016
Entry does not mention VirtualBox driver_version? I cant image this problem always existed. FWIW i have attached the output of "google-chrome --enable-gpu-service-logging --enable-gpu-debugging".
,
Dec 5 2016
,
Dec 6 2016
,
Jan 19 2018
FWIW - for posterity I noticed the next Linux kernel 4.16 is going to have integrated vboxguest driver, but has the same vendor_id and device_id. I wonder if the problem still does exist though.. since the driver functionality is now further integrated in the OS, like OpenGL pass-through. I would be happy to run a test if provided some details, aside from compiling chromium.
,
Jan 20 2018
You can try running 'google-chrome --ignore-gpu-blacklist' and see if original problems are resolved.
,
Mar 5 2018
Thanks! Sadly unable to test now because current VirtualBox 5.2.8r has a Ubuntu bug with 3D Acceleration on. (see https://forums.virtualbox.org/viewtopic.php?f=6&t=85073&start=15 ) I'll try again later. |
|||
►
Sign in to add a comment |
|||
Comment 1 by barryst...@gmail.com
, Oct 24 2016499 KB
499 KB View Download
51.3 KB
51.3 KB View Download