Bug 38866 – Firefox takes high CPU consumption during appliance setup on local machine

Bug 38866 - Firefox takes high CPU consumption during appliance setup on local machine


Summary:	Firefox takes high CPU consumption during appliance setup on local machine

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	System setup
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-07-09 11:56 CEST by Alexander Kläser
Modified:	2019-01-03 07:16 CET (History)
CC List:	1 user (show)

See Also:	https://bugzilla.mozilla.org/show_bug.cgi?id=508427 40985
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	UCS Performance
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexander Kläser

2015-07-09 11:56:27 CEST

Constant loads at 20-40% are quite common during the executing of setup-join.sh script. AFAIS, this has nothing to do with JavaScript, the JavaScript profiler does not show any high script load. Additionally, the CPU load remains stable at about 13% if nothing happens in the browser.

The following bug report might be related to this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=508427

Comment 1 Alexander Kläser

2016-08-01 14:42:49 CEST

There seems to be a workaround (https://bugzilla.mozilla.org/show_bug.cgi?id=508427#c131) for lowering the CPU load:
---------- 8< ---------- 
[...]
A little hunting around layout/base/nsRefreshDriver.cpp in the source code to firefox and I found "layout.frame_rate" which defaults to 60 frames/second (if set to -1 in the about:config page).  If in about.config I set layout.frame_rate to 10 then I would get about 10 wake ups per second. [ I am counting a wakup as a whole cycle of those poll()s, recvfrom()s and a read("\372") that you see in strace. ]  Set layout.frame_rate to 3 and you get 3 wakeup/sec.

With lower rate settings I get very slow/laggy UI responsiveness (for things like typing a new URI in the URI bar).  A rate of 15 is pretty usable, though, and yields about 4X less aggressive wake ups/second -- which for laptop battery people may be helpful.  So, at least on my system and I suspect others this seems to be a the "knob" to control the effect.  It also may answer some questions raised earlier about "which timer thread" and so forth.
[...]
---------- 8< ----------

Comment 2 Stefan Gohmann

2019-01-03 07:16:28 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.