1479223 - Hovering cursor over links causes high CPU and RAM usage

Status: NEW

(Core :: Layout, defect, P3)

Description

[get_logan]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180704003137

Steps to reproduce:

1. Go to http://buzzworthystudio.com/
2. Alternate hovering the cursor over the various links on that page


Actual results:

Eventually CPU and RAM usage will climb and seemingly never go back down until the tab is closed.


Expected results:

CPU and RAM should not have increased so dramatically. Chrome and Edge are not affected by this bug.

Comment 1

[get_logan]

Video capture of issue:
https://youtu.be/UCjK-9acMMc

Performance profile:
https://perfht.ml/2LXZbVj

Comment 2

[get_logan]

Attachment: memory-report.json.gz

Memory report

Comment 3

[get_logan]

Tested with Windows Defender disabled and using a new Firefox profile.

Comment 4

[Alice0775 White]

I can reproduce the huge memory usage on Win10 Nightly63.0a1.

Comment 5

[Alice0775 White]

Aha, I can also reproduce on Chrome Dev 69.0.3497.12 when you move the mouse pointer around the screen to draw a circle about a minute.

Comment 6

[get_logan]

(In reply to Alice0775 White from comment #5)
> Aha, I can also reproduce on Chrome Dev 69.0.3497.12 when you move the mouse
> pointer around the screen to draw a circle about a minute.

Heh, yeah I just tried Chrome Dev 69.0.3497.12 and Chrome Canary 70.0.3505.0. Both eventually crashed for me too when going for about a minute.

Wasn't able to reproduce on:
Microsoft Edge 42.17134.1.0, Microsoft EdgeHTML 17.17134
Chrome Stable 68.0.3440.75 and Beta 68.0.3440.75 (seems to be same build at this point in time?)

Looks like Chrome may have a regression? Even so, the Chrome builds that crashed are still more resilient to this bug than current Firefox Stable, Beta and Nightly.

Comment 7

[get_logan]

FYI, I created a bug report for Chrome Dev.
https://bugs.chromium.org/p/chromium/issues/detail?id=868711

Comment 8

[get_logan]

I just got Chrome Stable 68.0.3440.75 to eventually crash as well. Seems much harder to reproduce on Stable.

Comment 9

[David Olah]

I managed to reproduce the issue on Windows 10, Ubuntu 16.04 and Mac OS X, Nightly 63.0a1 (2018-07-31), Firefox 62.0b13 and Firefox 61.0.1.

I think it will be a good starting point to set the Layout component.