Firefox very slow on Windows ARM!
Categories
(Core :: Performance, defect)
Tracking
()
People
(Reporter: m.ernst, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0
Steps to reproduce:
Update FF to the latest version on a Windows ARM PC.
Actual results:
Firefox has become very bad on Windows ARM PC (Adreno 685 GPU)! After some display problems under version 127 (https://bugzilla.mozilla.org/show_bug.cgi?id=1898164) it got better for a short time: the graphics errors disappeared. BUT: in the meantime the FF under ARM is terribly slow! Not only the websites. Even the startup takes 3x as long as Chrome...in general: the whole handling is very slow. Have you probably simply (partially) deactivated HW acceleration?
FF is currently unusable under ARM!
Comment 1•2 months ago
|
||
Does it happen also on a clean Firefox profile?
https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems#w_start-firefox-in-troubleshoot-mode
Comment 2•2 months ago
|
||
- Please type "about:support" in your browser, and copy-paste its output here
- Please capture a profile when you experience the slow issue. See the guide here: https://profiler.firefox.com/ , https://profiler.firefox.com/docs/#/ . Please use the "Graphics" preset when capturing the profile.
Comment 3•2 months ago
|
||
Is this using the Firefox ARM build (https://www.mozilla.org/en-US/firefox/all/desktop-release/win64-aarch64/) or using the x86 build of Firefox?
Comment 4•2 months ago
|
||
This bug was moved into the Performance component.
:m.ernst, could you make sure the following information is on this bug?
- For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
- For memory usage issues, capture a memory dump from
about:memory
and attach it to this bug. - Troubleshooting information: Go to
about:support
, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.
If the requested information is already in the bug, please confirm it is recent.
Thank you.
Description
•