Opened 9 years ago
Last modified 7 years ago
#14985 reopened defect
Enable 3D acceleration cause black screen or flickering -> obsolete
Reported by: | maxchen | Owned by: | |
---|---|---|---|
Component: | 3D support | Version: | VirtualBox 5.0.12 |
Keywords: | 3D acceleration, hardware acceleration | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description
Ubuntu 14.04.3 X64 + mate 1.82 for both host and guest Enable 3D acceleration for guest VM enable hardware acceleration for Chrome in both guest and host for Chrome, flicking in VM, but works fine in host
the screen of VM will go black randomly, only can I sent ctrl-alt-backspace to restart X. However, after update both kernel to 4.2 (sudo apt-get install linux-generic-lts-wily). no more black screen in VM. But Chrome still flickering screen when launch if hardware acceleration is enable in its setings. A 4 seconds screen cast is on https://youtu.be/paVfpClhyj8
Change History (9)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Out of interest, is this still an issue with the update build on the Downloads page? Note that I did not do anything special to fix it.
follow-up: 5 comment:3 by , 9 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Summary: | Enable 3D acceleration cause black screen or flickering → Enable 3D acceleration cause black screen or flickering -> obsolete |
No response, closing. Please re-open if appropriate.
comment:4 by , 9 years ago
Resolution: | obsolete |
---|---|
Status: | closed → reopened |
Reopening because the same issue is happening to me:
ramy@ramy:~$ uname -a Linux ramy 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ramy@ramy:~$ chromium-browser --version Chromium 52.0.2743.116 Built on Ubuntu , running on Ubuntu 16.04 VirtualBox: Version 5.1.6 r110634 (Qt5.5.1) Latest Guest Additions installed
Started the browser generates the following:
ramy@ramy:~$ chromium-browser [7232:7232:0922/170330:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process. [7232:7232:0922/170330:ERROR:texture_manager.cc(2942)] [.DisplayCompositor-0x562e43759550]GL ERROR :GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_ENUM : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command OpenGL Warning: You called glBindTexture with a target of 0xde1, but the texture you wanted was target 0x8513 [1D: de0 2D: de1 3D: 806f cube: 8513] [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2214)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_OPERATION : ScopedTextureBinder::ctor: was unhandled [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2214)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_OPERATION : ScopedTextureBinder::ctor: was unhandled [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [7232:7232:0922/170330:ERROR:gles2_cmd_decoder.cc(2210)] [.CompositorWorker-0x562e43754d50]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
comment:5 by , 9 years ago
I just reopened it, please let me know if there is anymore information I can provide. Thanks.
Replying to michael:
No response, closing. Please re-open if appropriate.
comment:7 by , 9 years ago
Note though: not likely to be resolved in the near future, as we do not have resources free for working on the current 3D implementation for X11 guests, so this has been redefined as user-supported for now.
Please see the wiki page regarding user contributions to X11 guest 3D support.
comment:8 by , 7 years ago
I've experienced the same just now after upgrading to v5.2.6 from v5.2.4, I then upgraded my guest vm's Guest Additions to v5.2.6. Then after restarting, screen went black. My guest vm is Ubuntu 16.04 LTS amd64. My host is macOS High Sierra v10.13.2. As for the guest settings, my video memory is maxed out to 128MB and enabled 3D acceleration.
What I did as a workaround, I unchecked the 3D acceleration and after restarting, it has loaded the guest successfully, but I'm experiencing a slight slow rendering. So I downgraded my Virtualbox back to v5.2.4 and enabled again the 3D acceleration. Still black screen, I then unchecked the 3D acceleration, downgraded the Guest Addition back to v5.2.4, enabled the 3D acceleration and everything is good.
comment:9 by , 7 years ago
Please use the search functionality before waking up a dead ticket. This is a known issue, just go to the Downloads page, see the "Important" part and the new, updated additions.
I clean install the VM again. And find that:
black screen when entering or leaving fullscreen, and flicking/black if the screen size is changed.
video https://youtu.be/m76T-s78ibE