Closed
Bug 975193
Opened 10 years ago
Closed 11 months ago
Firefox takes always no more than about 1 CPU until it is to slow to work, even if there is more CPU available.
Categories
(Core :: Performance, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: lukasz.paszke, Unassigned, NeedInfo)
References
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release) Build ID: 20140212131424 Steps to reproduce: I tested it in safe mode and in normal mode and with completely new profile, it always repeats. It happens on latest Firefox 27.0.1 on OSX Maverics 10.9.1 and many recent versions of OSX Lion and Firefox including last ones. To reproduce it one must open as many tabs as possible with CPU intensive websites like javascript based http://bitcoinwisdom.com/markets/btce/btcusd. Actual results: CPU load will increase with number of tabs and load will end increasing on about 110% CPU no matter how many free CPU units there is in the system. Firefox works very well, with every next opened site increasing CPU load normally with about the same value, until it hits 100%. After 100% every new site is increasing load very little and every thing in the tabs begins to work very slow. I was able to get up to about 110% until everything was so slow that I was unable to load next site. Rest of the OSX was not affected by this slow down of Firefox. I think Firefox does it on my OSXs for a long time (months, maybe a year) but recently I realized what is going on. It is easy to reproduce with http://bitcoinwisdom.com/markets/btce/btcusd. Expected results: Firefox should be able to consume more then about 1 CPU easily and without slow down, that is Activity Monitor during high Firefox load should show more then 110% Firefox CPU usage. In the extreme case Firefox should be able to use 100% all Mac CPU resources. Currently when Firefox uses 110% CPU Activity Monitor shows about 25% usage of all Mac CPU resources. I almost quit Firefox when I realized that it could be a bug not reported since years, and it can be big factor in Firefox market share loses. It is quite difficult to realize that it is a bug.
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID 20160110030214 Tested on Mac OS version 10.9.5 with the Nightly 46.0a1 build. I can reproduce the problem. Tested with e10s disabled. CPU usage is lower and Firefox responds faster. Reporter, please try reproducing the bug with e10s disabled.
Status: UNCONFIRMED → NEW
Component: Untriaged → General
Depends on: e10s
Ever confirmed: true
Flags: needinfo?(lukasz.paszke)
Whiteboard: [MemShrink]
Version: 27 Branch → Trunk
Updated•8 years ago
|
Whiteboard: [MemShrink]
Reporter | ||
Comment 2•7 years ago
|
||
I tested. Nothing has changed about this problem. I am no longer using Firefox. Chrome is not so good like Firefox but much faster. Update of my report because I like Firefox and you people from Firefox: Steps to reproduce: It happens on latest Firefox 55.0.3 (64-bit) on OSX Sierra 10.12.6 on MacBook Pro (Retina, 15-inch, Mid 2015). To reproduce it one must open as many tabs as possible with CPU intensive websites like javascript based http://bitcoinwisdom.com/markets/btce/btcusd. Actual results: CPU load will increase with number of tabs and load will end increasing on about 100% CPU no matter how many free CPU units there is in the system. At the beginning Firefox works very well, and with every next opened site increasing CPU load normally with about the same value, until it hits 130%. After 100% every new site is increasing load very little and every thing in the tabs begins to work very slow. I was able to get up to about 130% until everything was so slow that I was unable to load next site. Rest of the OSX was not affected by this slow down of Firefox. Expected results: Firefox should be able to consume more then about 1 CPU easily and without slow down, that is Activity Monitor during high Firefox load should show more then 110% Firefox CPU usage. In the extreme case Firefox should be able to use 100% all Mac CPU resources. Currently when Firefox uses 110% CPU Activity Monitor shows about 25% usage of all Mac CPU resources.
Flags: needinfo?(lukasz.paszke)
Reporter | ||
Comment 3•7 years ago
|
||
I tested disabling e10s and it did not change anything. So I do not see improvement when e10s is disabled.
Dear developers of Firefox, I have 55.* version of Firefox at work and at home At work i have Windows 7 OS, at home the Ubuntu 16.04 LTE I have my own synced profile. I don't have problem with syncing... In both OSes i regulary and every day i see the situation when after few work time (may be even after 1-5 minutes) of Firefox i see the CPU 100% of Firefox and the Firefox hangs up after... Only one way i have for repairing of this: "killall -HUP firefox" command at Ubuntu and "End Task" in Windows. In both cases i have turned on option about "report health" and about "reports to Mozilla". I know about the page "about:crashes" and regulary to see there. The main problem is there: this hangings up cases are not generated there. When i killed the Firefox and restarted its i didn't see fresh some reports in "about:crashes". I tried to tun on safe mode too. In safe mode the Firefox has same buggy behaviour - after some minutes it starts to eat 100% of CPU and no responding after... And again in "about:crashes" doesn't have there any fresh generated reports (about:crashes sometime has reports there which were created by other situation - may be by like "segmentation faults" errors). I conclude that this "CPU bug" is not reported to you in many user cases! And i conclude that this is global problem (some OSes) not related with hardware and plugins. I don't know how to report about this to you. I love your browser but your last version (55.0.2 & 55.0.3) are very very buggy. This is very annoying! Best regards, Alexey
Reporter | ||
Comment 5•7 years ago
|
||
I tested it with a little bit different website https://bitcoinwisdom.com/markets/bitstamp/btcusd, and in this case it makes Firefox so lagged that it is almost irresponsive when I reached 10 separate Firefox windows open. I think there could be correlation with javascript. The sites with this issue are extensively using javascript. This kind of problem is usually related to some interprocess shared state, which must be synchronized between Tab processes. Sometimes this state is invisibly, unintentionally shared through some external library or OS. It is really difficult to track it down. My idea is you should run Firefox in deep debug mode and count processes parameters like number of sleeps, number of waiting sockets and system calls. When Firefox reaches 130% there should be some anomaly building in advanced process parameters statistics, e.g. increase of time spent in some functions.
Comment 6•7 years ago
|
||
FWIW, I don't see significant CPU use with 58.0b8 on thinkpad w520
Reporter | ||
Comment 7•7 years ago
|
||
I tested last Mac OS with FF Version 57.0.1 (64-bit) on OSX Sierra 10.12.6 on MacBook Pro (Retina, 15-inch, Mid 2015). Problem still the same. Firefox was unable to get more than 140% of CPUs and slows down in the way I described in this bug. I hate Chrome but still sentenced to Chrome.
Updated•2 years ago
|
Severity: normal → S3
Comment 8•11 months ago
|
||
Reporter, are you still experiencing this issue?
Flags: needinfo?(lukasz.paszke)
Updated•11 months ago
|
Component: General → Performance
Product: Firefox → Core
Comment 9•11 months ago
|
||
This bug was moved into the Performance component.
:lukasz.paszke, 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.
Flags: needinfo?(lukasz.paszke)
Comment 10•11 months ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:fdoty, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(lukasz.paszke) → needinfo?(fdoty)
Comment 11•11 months ago
|
||
Closing this bug due to inactivity on part of the reporter. If you believe this is done in error, please comment or open a new bug and reference this one.
Status: NEW → RESOLVED
Closed: 11 months ago
Flags: needinfo?(fdoty)
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•