Closed Bug 1400573 Opened 7 years ago Closed 7 years ago

http://www.experian.com unusable and high cpu even after tab closed

Categories

(Core :: Graphics, defect, P1)

57 Branch
defect

Tracking

()

RESOLVED FIXED
mozilla57
Tracking Status
firefox-esr52 --- unaffected
firefox55 --- unaffected
firefox56 --- unaffected
firefox57 --- fixed

People

(Reporter: mark, Assigned: mchang)

References

Details

(Keywords: regression, Whiteboard: [gfx-noted])

Attachments

(1 file)

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

Steps to reproduce:

Browse to http://www.experian.com/


Actual results:

Links and menu do not work.  Then close tab.  Nightly process stays stuck at ~25% CPU until process is killed in task manager.


Expected results:

Page should work.
This is my first attempt at actually running the regression tool, so hopefully I've done it correctly:

2017-09-16T09:46:01: INFO : Narrowed inbound regression window from [67888ae0, f84944ac] (3 builds) to [5ea410f1, f84944ac] (2 builds) (~1 steps left)
2017-09-16T09:46:01: DEBUG : Starting merge handling...
2017-09-16T09:46:01: DEBUG : Using url: https://hg.mozilla.org/integration/autoland/json-pushes?changeset=f84944ac039d2db1cbfcd521634ca12665710074&full=1
2017-09-16T09:46:01: DEBUG : Found commit message:
Bug 1392453: Allow limiting the blend surface area and the portion of the layer being resolved. r=mchang

This introduces the infrastructure to specify the bounds of drawing commands being executed. These bounds can then be used to limit operations done for blending in order to reduce required fillrate. Currently we only specify the bounds for DrawSurface but it would be easy to extend this for other drawing commands if so desired.

MozReview-Commit-ID: BUFJzphfdKc

2017-09-16T09:46:01: INFO : The bisection is done.
2017-09-16T09:46:01: INFO : Stopped
Has Regression Range: --- → yes
Blocks: 1392453
Component: Untriaged → Graphics
Keywords: regression
Product: Firefox → Core
Mark, are you running with any preferences modified?
Flags: needinfo?(mark)
Priority: -- → P1
Whiteboard: [gfx-noted]
Assignee: nobody → mchang
(In reply to Milan Sreckovic [:milan] from comment #2)
> Mark, are you running with any preferences modified?

I just tried with a new profile with the same results.  I also didn't add any custom preferences when running mozregression and didn't set a profile, so it should have used default preferences unless I'm mistaken.
Flags: needinfo?(mark)
Flags: needinfo?(bas)
This is probably because there's now a potential exponential cost operation if you'd keep using complex blends. I have an idea for a (somewhat ugly) fix, I'll test it and put it up.
Flags: needinfo?(bas)
I had an idea for a better fix and I've put it up on bug 1392453. My suggestion for fixing this bug is backing out 1392453.
Comment on attachment 8910266 [details]
Bug 1400573: Back out initial fix for bug 1392453.

https://reviewboard.mozilla.org/r/181762/#review187146
Attachment #8910266 - Flags: review?(mchang) → review+
Merged backout: https://hg.mozilla.org/mozilla-central/rev/c041f734d59f

Feel free to reopen if more is needed in here.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
Flags: qe-verify+
Reproduced the high cpu load and unresponsive menus on 2017-09-16 Nightly under Win 10 64-bit.

With Firefox 57 beta 13 the website is correctly loaded and the cpu stays at under 10% and then decreases under Win 10 64-bit and Ubuntu 16.04 64-bit.

On Mac OS X 10.13 on the other hand, the menus and links work properly, but the cpu is pretty high (Firefox + FirefoxCP Web Content ~80%) at first load and when opening sub-categories. CPU decreases after the page is loaded. 

Should this be considered as a follow-up issue? Thank you!
Flags: needinfo?(bas)
(In reply to Petruta Rasa [QA] [:petruta] from comment #10)
> Reproduced the high cpu load and unresponsive menus on 2017-09-16 Nightly
> under Win 10 64-bit.
> 
> With Firefox 57 beta 13 the website is correctly loaded and the cpu stays at
> under 10% and then decreases under Win 10 64-bit and Ubuntu 16.04 64-bit.
> 
> On Mac OS X 10.13 on the other hand, the menus and links work properly, but
> the cpu is pretty high (Firefox + FirefoxCP Web Content ~80%) at first load
> and when opening sub-categories. CPU decreases after the page is loaded. 
> 
> Should this be considered as a follow-up issue? Thank you!

Can you confirm this is working as expected on current nightly (something from late October)?
Flags: needinfo?(bas)
The behavior is the same on today's Nightly.
Please note that the cpu increase is not noticeable while browsing the website, only the Activity Monitor shows it.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: