Hardware acceleration in Firefox/SeaMonkey causes Oracle VirtualBox 3.2/4.0 to crash

RESOLVED FIXED

Status

()

RESOLVED FIXED
8 years ago
7 years ago

People

(Reporter: adriank, Unassigned)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
Created attachment 499742 [details]
Firefox rendering with hardware acceleration activated

When hardware acceleration is activated in Firefox 4 (beta8) or SeaMonkey 2.1 (b2pre) in a VirtualBox guest, then:
-the application renders badly and is in fact unusable (see screenshot)
-after some time (from a few seconds to a few minutes), the VM will crash completely

Without activated hardware acceleration, everything works fine.

Tested on a Mac OS X 10.6 32bit host and a Windows XP SP3 32bit guest with VirtualBox 3.2.12 and VirtualBox 4.0 Beta4.
Report the crash to the Virtualbox developers.
This is indeed a bug in VirtualBox from what I can see, we should look into how to detect it and blacklist their drivers.

Comment 3

8 years ago
the virtualbox bug tracker is: http://virtualbox.org/newticket (account required)
(Reporter)

Comment 4

8 years ago
The problem still exists (Firefox 4.0b9 & VirtualBox 4.0.2). Could the VirtualBox drivers be simply blacklisted please?
Sure, if we know how to identify them. Can you please go to about:support and paste the contents of the graphics section.

Comment 6

8 years ago
Here is about:support output:

  Graphics

        Adapter Description
        VirtualBox Graphics Adapter

        Vendor ID
        80ee

        Device ID
        beef

        Adapter RAM
        Unknown

        Adapter Drivers
        VBoxDisp

        Driver Version
        4.0.2.0

        Driver Date

        Direct2D Enabled
        false

        DirectWrite Enabled
        false (0.0.0.0)

        WebGL Renderer
        (WebGL unavailable)

        GPU Accelerated Windows
        0/1
Depends on: 623338

Comment 7

8 years ago
has someone filed a bug against virtualbox?

http://www.virtualbox.org/wiki/Bugtracker

has clear instructions for filing a bug. It's incredibly rude to file a bug asking blocklisting without filing a bug in another open bug tracker to inform the relevant team about the problem.

All you need to do is attach one log file which the application (virtualbox) readily provides.

Benoit: please do *NOT* blocklist until someone files a bug report (with the log file) to virtualbox.
(Reporter)

Comment 8

8 years ago
(In reply to comment #7)
> has someone filed a bug against virtualbox?

I didn't file a bug, because when filling this bug here, the VirtualBox guys asked to not file bugs, but report the problems in the forums (probably, because VirtualBox 4 was in beta at that time) and that's what I did: http://forums.virtualbox.org/viewtopic.php?f=15&t=37210&start=0#p167068 .

Comment 9

8 years ago
well, it's out of beta now. further as you had crashed in 3.2.x you could have legitimately filed it against that.

please file.

it isn't ok for virtualbox to crash.
(In reply to comment #6)
> Here is about:support output:
> 
>   Graphics
> 
>         Adapter Description
>         VirtualBox Graphics Adapter
> 
>         Vendor ID
>         80ee
> 
>         Device ID
>         beef

OK, PCI vendor ID 0x80ee is: Oracle Corporation - InnoTek Systemberatung GmbH

I confirm that their only device ID is 0xbeef:
http://www.pcidatabase.com/vendor_details.php?id=1695

So anyway, the second patch in bug 623338 makes us only whitelist Intel, NVIDIA and AMD/ATI vendors --- every other vendor gets blocked. So this bug will be fixed by it.
This has been fixed by the blocking of all non-intel/ati/nvidia vendors in bug 623338.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.