Closed
Bug 1381746
Opened 7 years ago
Closed 7 years ago
High CPU and memory usage with latest Firefox
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: rajeshcode, Unassigned)
Details
(Keywords: hang, perf, Whiteboard: [MemShrink])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.3; rv:54.0) Gecko/20100101 Firefox/54.0 Build ID: 20170628075643 Steps to reproduce: Browsing with latest Firefox (version 54), 5 to 7 tabs opened. Actual results: High CPU and memory usage with Firefox, due to this machine is became hang stage. Expected results: Normal browsing need to be happened.
Comment 1•7 years ago
|
||
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20170720030203 I have tested your issue on latest Nightly build and could not reproduce it. I have opened multiple tabs but the memory usage is in range. From what i can see, e10s is not enabled on your browser. Can you please retest this using latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/AR5o9d).
Flags: needinfo?(rajeshcode)
I have also tested the same issue with Firefox Nightly 56.0a1, and it is happening again. Already attached the screenshot with Three tabs, please the attachment- firefox-nightly.JPG
Comment 4•7 years ago
|
||
(In reply to rajeshcode from comment #3) > I have also tested the same issue with Firefox Nightly 56.0a1, and it is > happening again. Already attached the screenshot with Three tabs, please the > attachment- firefox-nightly.JPG Were you able to reproduce in safe mode [1]? Can you also provide the list of extension you're using from about:support? [1] https://support.mozilla.org/kb/troubleshoot-and-diagnose-firefox-problems#w_3-restart-firefox-in-safe-mode
Flags: needinfo?(rajeshcode)
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
Comment 6•7 years ago
|
||
rajeshcode has not replied to comment 4, so => incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(rajeshcode)
Resolution: --- → INCOMPLETE
Hi! I made some crashes by hands (crashfirefox.exe) in Windows 7 and in Unix through kill -ABRT What are the symptoms? In random moments the Firefox v56.* has only-one core CPU 100% eating. In Windows 7 (64bit) & Linux (Ubuntu 16.04 LTE 64bit) Reports are here: Ubuntu OS: https://crash-stats.mozilla.com/report/index/0b0e6273-26fb-482e-b033-c91be1171101 https://crash-stats.mozilla.com/report/index/237ae0e4-6eb2-4c8b-87e8-3c2471171101 https://crash-stats.mozilla.com/report/index/7ddfad60-8f3e-4495-a05f-5d6d21171110 https://crash-stats.mozilla.com/report/index/95468eb1-28b2-40f7-8f0c-8a7261171110 https://crash-stats.mozilla.com/report/index/cd310102-c547-486f-bbd3-0b7791171110 https://crash-stats.mozilla.com/report/index/6df179b4-721a-4440-97e5-059d21171110 Windows 7: https://crash-stats.mozilla.com/report/index/8e172c11-2367-43b1-98f2-128251171113#allthreads Best regards, Alexey
Comment 8•7 years ago
|
||
(In reply to Alexey from comment #7) > Hi! > > I made some crashes by hands (crashfirefox.exe) in Windows 7 and in Unix > through kill -ABRT > > What are the symptoms? In random moments the Firefox v56.* has only-one core > CPU 100% eating. In Windows 7 (64bit) & Linux (Ubuntu 16.04 LTE 64bit) > > Reports are here: > > Ubuntu OS: > > https://crash-stats.mozilla.com/report/index/0b0e6273-26fb-482e-b033- > c91be1171101 > https://crash-stats.mozilla.com/report/index/237ae0e4-6eb2-4c8b-87e8- > 3c2471171101 > https://crash-stats.mozilla.com/report/index/7ddfad60-8f3e-4495-a05f- > 5d6d21171110 > https://crash-stats.mozilla.com/report/index/95468eb1-28b2-40f7-8f0c- > 8a7261171110 > https://crash-stats.mozilla.com/report/index/cd310102-c547-486f-bbd3- > 0b7791171110 > https://crash-stats.mozilla.com/report/index/6df179b4-721a-4440-97e5- > 059d21171110 > > Windows 7: > > https://crash-stats.mozilla.com/report/index/8e172c11-2367-43b1-98f2- > 128251171113#allthreads > > Best regards, Alexey Alexey, thank you for the crash reports. This bug is closed, can you file a new bug for your issue and CC me on it? It looks like you might have a sqlite issue. You could try running in safe mode [1] to see if you still have problems and if that fixes things a Firefox refresh [2] might help. Let's followup in the new bug though. [1] https://support.mozilla.org/kb/troubleshoot-and-diagnose-firefox-problems#w_3-restart-firefox-in-safe-mode [2] https://support.mozilla.org/kb/refresh-firefox-reset-add-ons-and-settings
You need to log in
before you can comment on or make changes to this bug.
Description
•