1692451 - Slowness (especially YouTube) on older PC (AMD E-350D APU with Radeon(tm) HD Graphics, 1,4 GHz)

Status: UNCONFIRMED

(Core :: Graphics, defect)

Description

[Paul Menzel]

User Agent: Mozilla/5.0 (X11; Linux i686; rv:85.0) Gecko/20100101 Firefox/85.0

Steps to reproduce:

On an several years old ASRock E350M1 open https://youtube.com.

$ lscpu
Architecture:                    i686
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   36 bits physical, 48 bits virtual
CPU(s):                          2
On-line CPU(s) list:             0,1
Thread(s) per core:              1
Core(s) per socket:              2
Socket(s):                       1
Vendor ID:                       AuthenticAMD
CPU family:                      20
Model:                           2
Model name:                      AMD E-350D APU with Radeon(tm) HD Graphics
Stepping:                        0
CPU MHz:                         1600.000
CPU max MHz:                     1600,0000
CPU min MHz:                     800,0000
BogoMIPS:                        3199.96
Virtualization:                  AMD-V
L1d cache:                       64 KiB
L1i cache:                       64 KiB
L2 cache:                        1 MiB
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full AMD retpoline, STIBP disabled, RSB filling
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx
                                  fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_goo
                                 d nonstop_tsc cpuid extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cm
                                 p_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt 
                                 hw_pstate vmmcall arat npt lbrv svm_lock nrip_save pausefilter
$ free -h
               total        used        free      shared  buff/cache   available
Mem:           1,6Gi       392Mi       754Mi        30Mi       479Mi       1,1Gi
Swap:             0B          0B          0B`

Actual results:

It takes 20 seconds until the page is loaded.

Expected results:

The Web site should load faster.

Comment 1

[Paul Menzel]

Attachment: Content of about:support

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 3

[Paul Menzel]

Attachment: Content of about:support with basic compositor under X.Org

I just tested with the basic compositor, and it’s not much better. In a private window, it takes 16 seconds until the page is loaded and the privacy dialog appears. Please find the troubleshooting information attached.

Comment 4

[Robert Mader [:rmader]]

Removing this from Wayland and Webrender bugs per comment 3

Paul, does this happen for you as well with a fresh profile on nightly? And if so, could you provide us with a profile? It's very easy, see https://profiler.firefox.com/

Comment 5

[Paul Menzel]

(In reply to Robert Mader [:rmader] from comment #4)

Removing this from Wayland and Webrender bugs per comment 3

Paul, does this happen for you as well with a fresh profile on nightly? And if so, could you provide us with a profile? It's very easy, see https://profiler.firefox.com/

I captured the profile, but the upload failed (bug #1695611).

Comment 6

[u758202]

There are many open old bugs with "YouTube" in their titles, which makes it hard for users facing problems to find relevant reports.

Since many things have changed since this bug was discussed, and there was no progress on it, I believe it can be closed as "Incomplete" now.

People still using old computers to watch YouTube videos may benefit from using an extension that forces it to use H.264 streams, like h264ify-embed-fix.