1830081 - Massive glitches with 114 on Win10 inside a virtual machine if hardware rendering is enabled

Status: UNCONFIRMED

(Core :: Graphics: WebRender, defect)

Description

[diogo2002job]

Attachment: Firefox Interface Strange.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0

Steps to reproduce:

I was testing Firefox Nightly and when I open it on my pc, the whole weird interface appears full of icons etc.
This happens when I have Hardware Acceleration enabled, when I disable it, it goes back to normal.

Actual results:

Strange firefox interface.

Expected results:

Should have opened the browser normally.

Comment 1

[Gregory Pappas [:gregp]]

Please consider using mozregression to find the specific code change which introduced the issue.

Comment 2

[Rares Doghi, Desktop QA]

Hi @diogo2002job are you still seeing this issue in our latest builds ? if so can you please reach about:support in the url bar > Press Copy text to Clipboard > Paste into a notepad file and then attach the file to this report ?

Comment 3

[Ashley Hale [:ahale]]

It's also possible to use the Copy text to Clipboard button and then open a new attachment on this bug and paste into the new attachment text box, which is a little quicker :)

Comment 4

[Ashley Hale [:ahale]]

Triage - rating S3 as it is difficult to know if enabling hardware acceleration is expected to break without looking at about:support to confirm if this is a GPU we had to block due to driver bugs or not.

Comment 5

[diogo2002job]

(In reply to Rares Doghi, Desktop QA from comment #2)

Hi @diogo2002job are you still seeing this issue in our latest builds ? if so can you please reach about:support in the url bar > Press Copy text to Clipboard > Paste into a notepad file and then attach the file to this report ?

I haven't tested it now, since I stopped using the virtual machine I used to try out these versions of Firefox, if it happens to me again in the future, I'll contact you again.

Comment 6

[diogo2002job]

(In reply to Ashley Hale [:ahale] from comment #4)

Triage - rating S3 as it is difficult to know if enabling hardware acceleration is expected to break without looking at about:support to confirm if this is a GPU we had to block due to driver bugs or not.

I used a virtual machine on an Intel Graphics 3000

Comment 7

[diogo2002job]

(In reply to Ashley Hale [:ahale] from comment #3)

It's also possible to use the Copy text to Clipboard button and then open a new attachment on this bug and paste into the new attachment text box, which is a little quicker :)

Ok, Thank You!

Comment 8

[diogo2002job]

(In reply to diogo2002job from comment #6)

(In reply to Ashley Hale [:ahale] from comment #4)

Triage - rating S3 as it is difficult to know if enabling hardware acceleration is expected to break without looking at about:support to confirm if this is a GPU we had to block due to driver bugs or not.

I used a virtual machine on an Intel Graphics 3000.

Comment 9

[diogo2002job]

(In reply to diogo2002job from comment #6)

(In reply to Ashley Hale [:ahale] from comment #4)

Triage - rating S3 as it is difficult to know if enabling hardware acceleration is expected to break without looking at about:support to confirm if this is a GPU we had to block due to driver bugs or not.

I used a virtual machine on an Intel Graphics 3000.

Comment 10

[Darkspirit]

Which virtualization software have you been using? VMWare?
Have you been using Picture-In-Picture when the glitch started occuring? bug 1812982 has been fixed in 115.

Comment 11

[diogo2002job]

(In reply to Darkspirit from comment #10)

Which virtualization software have you been using? VMWare?
Have you been using Picture-In-Picture when the glitch started occuring? bug 1812982 has been fixed in 115.

Yes, VMWare.
No, I didn't use that feature.