Ticket #11576 (closed defect: obsolete)

Opened 9 years ago

Last modified 6 years ago

Windows 7 Guest Renders Chrome backwards and sheared

Reported by: ju2wheels Owned by:
Component: 3D support Version: VirtualBox 4.2.8
Keywords: Cc:
Guest type: Windows Host type: Linux


There is a problem rendering the latest Google Chrome in Windows 7 64bit guest running on Ubuntu 12.04 LTS host with guest additions installed, 3d accel enabled. This was also happening with 4.2.6 but I dont recall if it started before that or not.

Attached image of shearing as example.


28.png Download (268.5 KB) - added by ju2wheels 9 years ago.

Change History

Changed 9 years ago by ju2wheels

comment:1 Changed 9 years ago by ju2wheels

This is still happening with 4.2.10, however I did find a fix describe here for a similar issue that happened with Linux guests:

It seems this bug is due to use of accelerated compositing on the Windows guest, so when you disable this feature on chrome it starts working normally.

comment:2 Changed 9 years ago by rugubara

the bug is still there on version 4.3.0

comment:3 Changed 9 years ago by misha

Please attach a VM log file for the issue with VBox 4.3.

comment:4 Changed 9 years ago by 3vi1J

I see this same bug in version 4.3 as well, running on 64-bit Ubuntu 13.10 with a *32-bit* Win7 guest. The VM itself shows no issue, other than the rendering in the Chrome window being totally corrupt.

Last edited 9 years ago by 3vi1J (previous) (diff)

comment:5 Changed 9 years ago by misha

Please attach a VM log here! Without it we won't be able to help.

comment:6 Changed 9 years ago by FlorianSteller

I'm using VM 4.3.6 for MC with an Windows 8.1 Guest. In the webkit(/blink) browser Chrome and latest Opera the pages repeatedly get scrambled while having 3d accel enabled. Firefox and IE are working fine. How can I make a logfile to help you?

comment:7 Changed 8 years ago by jcsanyi

I'm also seeing this issue on 4.3.6, running a 64-bit Windows 7 guest on a 64-bit Arch Linux host. Disabling 3d acceleration (in either the vm, or in Chrome) seems to temporarily resolve the issue.

I'd also be happy to provide any logs that are required if you provide some instructions on how to go about generating them.

comment:8 Changed 8 years ago by ju2wheels

vm log should be in ~/VirtualBox VMs/<VM Name>/Logs/VBox.log for anyone that has time to do it.

Edit: Probably should just tarball up all the logs in there, not just the first one.

Last edited 8 years ago by ju2wheels (previous) (diff)

comment:9 Changed 8 years ago by Yuvi

I'm seeing this issue on Virtualbox 4.3.6_OSE_r91406 with Windows7_SP1_N_64bits guest (3D Support active) on an ArchLinux 64b host. Procedure of my log file:

  • clear log
  • start W7
  • start Chrome => CTRL+C
  • shutdown W7

But I seen any information about GoogleChrome.

comment:10 Changed 6 years ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use