1312083 - bad scrolling since update from 49.0.1 to 49.0.2

Status: RESOLVED INVALID

(Core :: Graphics, defect, P3)

Description

[Frank Tank]

User Agent: Mozilla/5.0 (Windows NT 10.0; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20161019084923

Steps to reproduce:

update from 49.0.1 to 49.0.2
49.0.1 was absolutely fine - very smooth


Actual results:

scrolling behaviour is very ugly with 49.0.2
it looks a little bit like a tearing effect and it is not smooth
so it is very hard to look at it and text is not readable while scrolling

- hardwareacceleration is on (no big effect if set to off)
- I´ve set "browser.tabs.remote.force" to enable (no big effect if set to disable)
- I´ve tried a new ff-profile (no effect)


Expected results:

should scroll smooth as 49.0.1

Comment 1

[Loic]

Could you type about:support in the location bar and copy here the section "graphics".

Comment 2

[Kartikaya Gupta (email:[e-mail])]

(In reply to Frank from comment #0)
> - hardwareacceleration is on (no big effect if set to off)
> - I´ve set "browser.tabs.remote.force" to enable (no big effect if set to
> disable)

Do you mean browser.tabs.remote.force-enable? The pref you quoted doesn't do anything. Also, by "no big effect", do you mean you still see the bug under those conditions?

Comment 3

[Frank Tank]

@Loic - unfortunately in german language:

Allgemeine Informationen
------------------------

Name: Firefox
Version: 49.0.2
Build-ID: 20161019084923
Update-Kanal: release
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:49.0) Gecko/20100101 Firefox/49.0
Betriebssystem: Windows_NT 10.0
Fenster mit mehreren Prozessen: 1/1 (aktiviert durch Benutzer)
Abgesicherter Modus: false

Grafik
------

Allgemeine Merkmale
Compositing: Basic
Asynchrones Wischen und Zoomen: Mausrad-Eingabe aktiviert
WebGL-Renderer: Google Inc. -- ANGLE (NVIDIA GeForce 7600 GT Direct3D9Ex vs_3_0 ps_3_0)
H264-Dekodierung durch Hardware: No; Hardware video decoding disabled or blacklisted
DirectWrite: false (10.0.10586.633)
GPU 1
Aktiv: Ja
Beschreibung: NVIDIA GeForce 7600 GT
Herstellerkennung: 0x10de
Gerätekennung: 0x0391
Treiber-Version: 9.18.13.908
Treiber-Datum: 1-30-2015
Treiber: nvd3dum
Subsys-ID: 06301462
RAM: 256

Weitere Informationen
AzureCanvasAccelerated: 0
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
failures: [GFX1-]: [D3D11] create component blender failed: 0x80070057, 0
Entscheidungsprotokoll
D3D9_COMPOSITING:
disabled by default: Disabled by default
DIRECT2D:
failed by runtime: Direct3D11 device does not support texture sharing
D3D11_HW_ANGLE:
broken by runtime: RenderTargetViews need recreating

Fehlerprotokoll
(#0) Error: [D3D11] create component blender failed: 0x80070057, 0
(#11) Error: [D3D11] create component blender failed: 0x80070057, 0
(#12) Error: [D3D11] create component blender failed: 0x80070057, 0
(#13) Error: [D3D11] create component blender failed: 0x80070057, 0
(#14) Error: [D3D11] create component blender failed: 0x80070057, 0
(#15) Error: [D3D11] create component blender failed: 0x80070057, 0
(#16) Error: [D3D11] create component blender failed: 0x80070057, 0
(#17) Error: [D3D11] create component blender failed: 0x80070057, 0
(#18) Error: [D3D11] create component blender failed: 0x80070057, 0
(#19) Error: [D3D11] create component blender failed: 0x80070057, 0
(#20) Error: [D3D11] create component blender failed: 0x80070057, 0
(#21) Error: [D3D11] create component blender failed: 0x80070057, 0
(#22) Error: [D3D11] create component blender failed: 0x80070057, 0
(#23) Error: [D3D11] create component blender failed: 0x80070057, 0
(#24) Error: [D3D11] create component blender failed: 0x80070057, 0
(#25) Error: [D3D11] create component blender failed: 0x80070057, 0

Comment 4

[Frank Tank]

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #2)

sorry i´ve menat "browser.tabs.remote.force-enable" 
i´ve checked twice: its hard to see a difference between "true" and "false" setting. Maybe scrolling is a little bit better if set to "true". But not that much - both are much worse than 49.0.1.

If I look at my last post I think there is something wrong with the Graphics.
Graphic rendering seems to be slower than normal while scrolling.

Comment 5

[Kartikaya Gupta (email:[e-mail])]

Thanks for the info. Can you try a couple of things:
1) Set dom.ipc.plugins.asyncdrawing.enabled to false, restart the browser, and see if you still have the issue.
2) Set layers.allow-d3d9-fallback to true, restart the browser, and see if you still have the issue.

If either of these changes improves your scrolling experience (back to the 49.0.1 quality) then we'll know what broke it for you. Thanks!

Comment 6

[Kartikaya Gupta (email:[e-mail])]

For reference the pushlog for 49.0.1 to 49.0.2 is this:

http://hg.mozilla.org/releases/mozilla-release/pushloghtml?fromchange=FIREFOX_49_0_1_RELEASE&tochange=FIREFOX_49_0_2_RELEASE

Comment 7

[Frank Tank]

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #5)
> Thanks for the info. Can you try a couple of things:
> 1) Set dom.ipc.plugins.asyncdrawing.enabled to false, restart the browser,
> and see if you still have the issue.
I will try this another day and report then
> 2) Set layers.allow-d3d9-fallback to true, restart the browser, and see if
> you still have the issue.
I did that already yesterday but didn´t report because I have no clue if that fixes the issue completely. :-)
But as far as I can see the scrolling experience is back to 49.0.1 quality.
It seems to me that the update sets the graphics adapter to not compatible with FF - maybe because there is no official support for Geforce7600 in Win10.(?)

here is the "Graphics" section with layers.allow-d3d9-fallback set to true (if it helps):

Grafik
------

Allgemeine Merkmale
Compositing: Direct3D 9
Asynchrones Wischen und Zoomen: Mausrad-Eingabe aktiviert
WebGL-Renderer: Google Inc. -- ANGLE (NVIDIA GeForce 7600 GT Direct3D9Ex vs_3_0 ps_3_0)
H264-Dekodierung durch Hardware: No; Hardware video decoding disabled or blacklisted
DirectWrite: false (10.0.10586.633)
GPU 1
Aktiv: Ja
Beschreibung: NVIDIA GeForce 7600 GT
Herstellerkennung: 0x10de
Gerätekennung: 0x0391
Treiber-Version: 9.18.13.908
Treiber-Datum: 1-30-2015
Treiber: nvd3dum
Subsys-ID: 06301462
RAM: 256

Weitere Informationen
AzureCanvasAccelerated: 0
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
failures: [GFX1-]: [D3D11] create component blender failed: 0x80070057, 0
Entscheidungsprotokoll
D3D9_COMPOSITING:
disabled by default: Disabled by default
available by user: Enabled via layers.allow-d3d9-fallback
DIRECT2D:
failed by runtime: Direct3D11 device does not support texture sharing
D3D11_HW_ANGLE:
broken by runtime: RenderTargetViews need recreating

Fehlerprotokoll
(#0) Error: [D3D11] create component blender failed: 0x80070057, 0
(#1) Error: [D3D11] create component blender failed: 0x80070057, 0
(#2) Error: [D3D11] create component blender failed: 0x80070057, 0
(#3) Error: [D3D11] create component blender failed: 0x80070057, 0
(#4) Error: [D3D11] create component blender failed: 0x80070057, 0
(#5) Error: [D3D11] create component blender failed: 0x80070057, 0
(#6) Error: [D3D11] create component blender failed: 0x80070057, 0
(#7) Error: [D3D11] create component blender failed: 0x80070057, 0

Comment 8

[Frank Tank]

Here comes the result for: dom.ipc.plugins.asyncdrawing.enabled = false

It has no effect on the graphics issue

Comment 9

[Kartikaya Gupta (email:[e-mail])]

Thanks. So it sounds like this is a result of the layers.allow-d3d9-fallback change.

Comment 10

[Milan Sreckovic [:milan] (needinfo for best results)]

Sure, I would expect accelerated compositor to work better.  This would only be a regression compared to 49 and 49.0.1, not a regression compared to 48.

Comment 11

[Kartikaya Gupta (email:[e-mail])]

Frank, can you confirm that the behaviour in 49.0.2 is more or less the same as in 48?

Comment 12

[Frank Tank]

No, I´ve noticed no such issues on 48

Comment 13

[Kartikaya Gupta (email:[e-mail])]

Can you post your about:support (Informationen and Grafik sections) from 48?

Comment 14

[Frank Tank]

Kartikaya, could you please assist me to do that?
Whats the best way to go back to 48? Should I simply downgrade my installation or install a 2nd FF in a different directory for example?

Comment 15

[Kartikaya Gupta (email:[e-mail])]

Frank, you can install in a different directory, it will probably be easier than downgrading your existing installation. You can even use a new profile to ensure your existing settings aren't modified.

Comment 16

[Frank Tank]

I´ve installed FF 48 in a differet directory with a new profile now. And it has the graphical issue too.
(That´s strange because I´m quite sure that there was no issue while I was on FF 48 previously)

about:support:

Allgemeine Informationen
------------------------

Name: Firefox
Version: 48.0.2
Build-ID: 20160823121617
Update-Kanal: release
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:48.0) Gecko/20100101 Firefox/48.0
Betriebssystem: Windows_NT 10.0 x86
Fenster mit mehreren Prozessen: 0/1 (deaktiviert)
Abgesicherter Modus: false

Grafik
------

Allgemeine Merkmale
Compositing: Basic
Asynchrones Wischen und Zoomen: nichts
WebGL-Renderer: Google Inc. -- ANGLE (NVIDIA GeForce 7600 GT Direct3D9Ex vs_3_0 ps_3_0)
H264-Dekodierung durch Hardware: No; Hardware video decoding disabled or blacklisted
DirectWrite: false (10.0.10586.633)
GPU 1
Aktiv: Ja
Beschreibung: NVIDIA GeForce 7600 GT
Herstellerkennung: 0x10de
Gerätekennung: 0x0391
Treiber-Version: 9.18.13.908
Treiber-Datum: 1-30-2015
Treiber: nvd3dum
Subsys-ID: 06301462
RAM: 256

Weitere Informationen
AzureCanvasAccelerated: 0
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
failures: [GFX1-]: [D3D11] create component blender failed: 0x80070057, 0
Fehlerprotokoll
(#0) Error: [D3D11] create component blender failed: 0x80070057, 0

Comment 17

[Kartikaya Gupta (email:[e-mail])]

Ok, I guess for now it looks like no regression between 48 and 49.0.2, since you are seeing the graphical issues in both cases. So I'm going to close this bug. If you discover why you weren't seeing the graphical issues on 48 before let us know.

Comment 18

[Frank Tank]

Thanks for your time spent on my bugreport...

but one last question:
does all that mean, that the problem is already fixed or will be fixed in the next version(s)?
Because I´ve tied the actual nightly version (52.0a1) and it has also the graphical issue.

Comment 19

[Kartikaya Gupta (email:[e-mail])]

No, I guess it means we don't consider this a bug per se, because this isn't really a regression (it was always like this).

Comment 20

[Frank Tank]

Sorry for the late reply.
Hmm, then it was always wrong(?)
Maybe its not a bug per se, but turning off hardware acceleration per default despite it does exist and its working well sounds more like a wrong FF default setting to me.

Comment 21

[Kartikaya Gupta (email:[e-mail])]

"Working well" depends on the individual user. It might work well for you but not work well for many other users (and I believe that is the case here, which is why it's turned off by default).

Comment 22

[Frank Tank]

OK, that´s maybe true. If there is a reason to deactivate acceleration, I´ll have to live with the issue.
Maybe I´m wrong because I´m not in-depth information about all that but I can´t see a real reason - except there is no official nvidia Driver for Win10 because it is out of support by nvidia.
If that is the only problem I think acceleration should be turned on by default. A 10year old GPU should work without changing settings manually.
If it is not as easy I will not further bother you with this :-)

(Just for information:
I use driver 309.08 wich is the last driver available for Win8.0. Normally Win10 can use the same drivers like Win8)

Comment 23

[Milan Sreckovic [:milan] (needinfo for best results)]

If you're not seeing the problems, I would set those preferences that give you the acceleration back.  We have disabled this because of really bad problems some people encounter, and because not everybody is as dedicated as you to share the information directly with us in bugzilla :) we are disabling it for a larger group than probably necessary.