VirtualBox

Opened 11 years ago

Closed 8 years ago

#11576 closed defect (obsolete)

Windows 7 Guest Renders Chrome backwards and sheared

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

Description

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.

Attachments (1)

28.png (268.5 KB ) - added by Julio Lajara 11 years ago.

Download all attachments as: .zip

Change History (11)

by Julio Lajara, 11 years ago

Attachment: 28.png added

comment:1 by Julio Lajara, 11 years ago

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: http://beshoy.girgis.us/2012/11/virtualbox-ubuntu-chrome-rendering-issue/

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 by rugubara, 10 years ago

the bug is still there on version 4.3.0

comment:3 by misha, 10 years ago

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

comment:4 by 3vi1J, 10 years ago

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 10 years ago by 3vi1J (previous) (diff)

comment:5 by misha, 10 years ago

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

comment:6 by FlorianSteller, 10 years ago

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 by jcsanyi, 10 years ago

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 by Julio Lajara, 10 years ago

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

http://www.virtualbox.org/manual/ch12.html#idp53980624

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

Last edited 10 years ago by Julio Lajara (previous) (diff)

comment:9 by Yuvi, 10 years ago

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. http://en.file-upload.net/download-8656420/VBox.log.html

comment:10 by aeichner, 8 years ago

Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use