Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Firefox freezes when using touch screen, gets back to normal after moving physical mouse or pressing any key on physical keyboard

  • 7 отговора
  • 1 има този проблем
  • 1 изглед
  • Последен отговор от marcin.miodek

more options

Lenovo Yoga 2 10 Tablet (1051f) - Bad performance when using touch screen, good performance when using mouse+keyboard

MAIN ISSUE: When using touch display as input method, the performance in Firefox (59.0.1) is very bad - there are multiple freezes and various other issues. The issues go away when using an external mouse+keyboard via USB.

FURTHER DETAILS: The most frustrating issues appear when: -switching between various open tabs in FF -closing and opening new tabs -right clicking on a tab > selecting "pin tab" - instead of pinning the tab, FF opens the website in a new window - it can be then dragged-into the original FF window, and pinned without problem -The general performance seems very bad and not what you would expect it to be

WHAT HELPS: -Connecting a mouse+keyboard through USB - then the performance is what I would expect from this hardware

VIDEOS SHOWING THE ISSUE: 1) Recording showing bad performance when using touch input: https://www.youtube.com/watch?v=mq1QYrXUlYE Note how clicking on the "multitasking" button at the bottom of the screen (I don't know the real name) interrupts the freeze, and then performance is back to normal... for some time.

2) Freeze when using touch input: https://www.youtube.com/watch?v=_4csda5Kdl0 What this video is showing: -touching the display - everything is frozen, tablet does not react to touches -then the physical mouse is moved (just moved! no clicking!) -you can then see sudden "update" of what was done using touch input, and everything returns to normal

3) Another instance of the same thing as in point 2: https://www.youtube.com/watch?v=9cHMTv0A2gE

4) Recording showing good performance when using mouse+keyboard as input devices: https://www.youtube.com/watch?v=2czwhvmdcAM

I have tried many suggested fixes already, but I will not be listing them here as I will be happy to re-test them.

Thank you in advance for any feedback and solutions.

Lenovo Yoga 2 10 Tablet (1051f) - Bad performance when using touch screen, good performance when using mouse+keyboard MAIN ISSUE: When using touch display as input method, the performance in Firefox (59.0.1) is very bad - there are multiple freezes and various other issues. The issues go away when using an external mouse+keyboard via USB. FURTHER DETAILS: The most frustrating issues appear when: -switching between various open tabs in FF -closing and opening new tabs -right clicking on a tab > selecting "pin tab" - instead of pinning the tab, FF opens the website in a new window - it can be then dragged-into the original FF window, and pinned without problem -The general performance seems very bad and not what you would expect it to be WHAT HELPS: -Connecting a mouse+keyboard through USB - then the performance is what I would expect from this hardware VIDEOS SHOWING THE ISSUE: 1) Recording showing bad performance when using touch input: https://www.youtube.com/watch?v=mq1QYrXUlYE Note how clicking on the "multitasking" button at the bottom of the screen (I don't know the real name) interrupts the freeze, and then performance is back to normal... for some time. 2) Freeze when using touch input: https://www.youtube.com/watch?v=_4csda5Kdl0 What this video is showing: -touching the display - everything is frozen, tablet does not react to touches -then the physical mouse is moved (just moved! no clicking!) -you can then see sudden "update" of what was done using touch input, and everything returns to normal 3) Another instance of the same thing as in point 2: https://www.youtube.com/watch?v=9cHMTv0A2gE 4) Recording showing good performance when using mouse+keyboard as input devices: https://www.youtube.com/watch?v=2czwhvmdcAM I have tried many suggested fixes already, but I will not be listing them here as I will be happy to re-test them. Thank you in advance for any feedback and solutions.

Всички отговори (7)

more options

Sorry for the formatting. I don't see "edit" option. The "-" should be actually in new lines.

more options

hi, does it make any difference when you try the following?: go to the firefox menu ≡ > options > privacy & security panel and under permissions check the setting to prevent accessibility services from accessing your browser.

more options

philipp said

hi, does it make any difference when you try the following?: go to the firefox menu ≡ > options > privacy & security panel and under permissions check the setting to prevent accessibility services from accessing your browser.

Tried that. Nope, does not help.

more options

could you try capturing a performance profile while the slowness is ongoing and sharing that with us? https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem

more options

Captured files: https://drive.google.com/open?id=1L8ug5arwgFnUgro2HVmUfULredoRW6l2

right-click-freeze.gz - triggered the freeze by right clicking (touch and hold) on an opened tab. Waited a few seconds, then moved the physical mouse to fix the freeze. Then captured the profile.

right-click-freeze2.gz - same as above

pin-tab-opens-in-new-window.gz - opened new tab, right clicked (touch and hold), selected "pin tab". Instead of pinning, the website opened in a new window.

It seems that _maybe_ the issue is that when using touch+hold option, the left mouse button becomes permanently pressed? It is just an idea.

Also, I am using Chrome now and it runs perfectly smooth - just confirming this is a FF issue only. :)

more options

thanks. the hangs all seem to be in the same nsBaseDragService::InvokeDragSession function - however i'm unsure how to troubleshoot this - could you file a bug for this on bugzilla.mozilla.org about this issue so that maybe some developers will take a look at this?