Open Bug 1486362 Opened 2 years ago Updated 11 months ago

CPU usage is extremely high at githubuniverse.com

Categories

(Core :: Layout, enhancement, P3)

57 Branch
Unspecified
Linux
enhancement

Tracking

()

Tracking Status
firefox63 --- affected

People

(Reporter: karlcow, Unassigned)

References

()

Details

(Whiteboard: [webcompat] [qf:p3])

This is a spin-off of https://webcompat.com/issues/12426
This page contains a lot of animations, slowly down the computer with very high cpu consumption.

Marking as a performance bug.
There are two problems causing the high cpu usage.

1) animation on #intro-icon element which is driven by script (requestAnimationFrame or setTime or some such)
2) transform animation on invisible elements (bug 1427033)
Firefox 56 and Firefox 57 are ancient unsupported versions. 
Why was this task reported instead of testing with a supported version?
Summary: CPU usage is extremely high both on Firefox 56.0 and 57.0 (Beta 8). All the other pages related to this GitHub event are having the same problem. On Chromium for Linux the CPU usage is normal. → CPU usage is extremely high at githubuniverse.com
Whiteboard: [webcompat] [qf] → [webcompat] [qf:p3:f67]
(In reply to Andre Klapper from comment #2)
> Firefox 56 and Firefox 57 are ancient unsupported versions. 
> Why was this task reported instead of testing with a supported version?

This was simply filed back when those were the latest versions, at the webcompat link in comment 0. I've clarified the summary here to not be version-specific.

Anyway -- mstange says that this is likely a result of the fact that we use software compositing on Linux for now, which is inherently slow.  (The reporter was using linux, per first comment on the original webcompat issue.)
Whiteboard: [webcompat] [qf:p3:f67] → [webcompat] [qf:p3]

Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.

Webcompat Priority: --- → ?

See bug 1547409. Migrating whiteboard priority tags to program flags.

Webcompat Priority: ? → ---
You need to log in before you can comment on or make changes to this bug.