1328152 - Scrolling too fast causes the screen to freeze

Status: UNCONFIRMED

(Core :: Graphics, defect, P3)

Description

[Serphentas]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
Build ID: 20170102030204

Steps to reproduce:

Go on a page where you can scroll with easy. Proceed with scrolling. Observe the screen locking up. If scrolling very slowly, no lock should be triggered.

Arrow keys have the same effect, but Home/End/Page up/down keys are fine.


Actual results:

The screen freezes, but background tasks (such as music playback) continue, implying it is only a 2D problem.


Expected results:

Normal scrolling without freezes.

Comment 1

[Loic]

Is it reproducible with the stable release? or only with Nightly?
https://www.mozilla.org/en-US/firefox/all/

Did you test with multi-process (e10s) disabled in about:preferences#general?

Comment 2

[Serphentas]

Without e10s it appears to be OK. Note that when Firefox has been open for some time (few hours), locks happen much less often. Restarting the computer brings back the problem.

I haven't tested stable yet.

Comment 3

[Serphentas]

Correction: it also does it without e10s. Will try stable soon.

Comment 4

[ovidiu boca[:Ovidiu]]

Can you please add a link that you used for this issue, it will be more easy to compare results. Can you please see if in safe mode is reproducible?  https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Comment 5

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

Are you by any chance running a non-compositing window manager in Linux?

Comment 6

[Serphentas]

(In reply to ovidiu boca[:Ovidiu] from comment #4)
> Can you please add a link that you used for this issue, it will be more easy
> to compare results. Can you please see if in safe mode is reproducible? 
> https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-
> mode

This one is pretty long, which works perfectly to trigger the effet: https://en.wikipedia.org/wiki/Taylor_series

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #5)
> Are you by any chance running a non-compositing window manager in Linux?

I'm running a standard install of Linux Mint so I assume no.

Comment 7

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

I'm not too familiar with Linux Mint but from the website it looks like 17.1 at least might be non-compositing by default. See the screenshot at [1] (which is embedded in the page at [2]) - can you try checking the "Use compositing" checkbox in that settings panel and see if that makes any difference?

[1] https://www.linuxmint.com/pictures/screenshots/rebecca/mintdesktop.png
[2] https://www.linuxmint.com/rel_rebecca_mate_whatsnew.php

Comment 8

[Serphentas]

Actually I can choose in which mode to operate, see http://pasteboard.co/jL08lnCGd.png

Comment 9

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

Does toggling that compositing option make any difference?

Comment 10

[Serphentas]

Tried on/off and fullscreen/windowed (all 4 cases) but no luck.

I currently have 4 screens, split in 2/2 on two video cards. I'll try without the second GPU, for it may sort things out.

Comment 11

[Serphentas]

I have found something interesting:

When booting with the Xen hypervisor loaded, KVM is not present:

> INFO: Your CPU does not support KVM extensions
> KVM acceleration can NOT be used

and freezes occur. I have tried disabling hardware acceleration, but no luck.

However, when booting without the Xen hypervisor, no freeze occurs at all. Everything works as it should.

This leads me to believe that somewhere in the 2D layer of either Firefox or the GPU driver, something changes in a way that affects the browser, because KVM is not present (or because of Xen).

Any ideas ?

Comment 12

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

Hm. Lee, does this sound familiar at all? ^

Comment 13

[Lee Salzman [:lsalzman]]

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #12)
> Hm. Lee, does this sound familiar at all? ^

I don't believe I've encountered something like this before.

Comment 14

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

Moving to graphics because it doesn't sound particularly APZ-related. Specially given that it happens with arrow-key scrolling (see comment 0) which is not going through APZ.

Comment 15

[Gregory Pappas [:gregp]]

Reporter, are you still experiencing this issue?