Closed Bug 1423180 Opened 7 years ago Closed 7 years ago

57.0.1 multiprocessor xeon tab lockup

Categories

(Core :: DOM: Content Processes, defect)

Product:
Core
Component:
DOM: Content Processes
Version:
57 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: genesis, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171128222554 Steps to reproduce: Environment: Hardware: HP xw8600 workstation with 2 xeon x5460 and 32GB RAM (2 CPU-sockets!) Software: Firefox 57.0.1 on Win10(v1703 b15063.726), new profile created, safe mode enabled Suspicion: Multiprocessor-Bug! Using FF with many tabs open Actual results: Many open tabs (80-130), some pinned, most not. With previous Version we had Problems that the whole browser ground to a halt. Restarting helps for a short time. Now ist is only some tabs, which do not load at all (new tab, just the moving dot, but the next new tab works) or grind to a halt sooner or later. Mostly the tab I am working on stops … very bad! It is very interesting, that FF57 uses way less memory, previous version took 6GB, now its often less than 0,5GB, but that does not help, when its unusable. CPU-usage for the whole system: ~20% Chrome and Edge work well, but I would like firefox to work. LAN-Infrastructure: Fritzbox 7590, Raspi with Pihole. All single-CPU-socket systems (mostly HP xw4600) in the LAN work well with FF57. Expected results: No tabs should lock up ... or only certain ones, but not randomly. Open up a new empty tab should not lock the tab up, while the next opened tab works again. Reloading a locked up tab does not help. Only a restart of the browser helps for a very short time. Starting a new window does not help, the tabs lock up whenever they "want to".
In that state, Firefox "ignores" the request to close via clicking the "X" in the UI. Very, very strange! Closing via taskbar or taskmanager works.
Some tabs remain useable (e.g. this one), while others (right now whatsapp-web) get incredibly slow (altough none of the CPUs is over 50%). If I try to use FF on a P4 2600 the CPU is just maxed out - no problem, that is not good, but seems normal. But here tabs just do not react, like typing in WA-web and the letters appear 30s later ... And the Hardware is way fast enough ... is ist not?
Component: Untriaged → Tabbed Browser
Component: Tabbed Browser → DOM: Content Processes
Product: Firefox → Core
Do you need any more details? Please ask!
Can you please record a performance profile when this happens, save the profile and share the link? https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem
Flags: needinfo?(genesis)
A couple of days ago the problem disappeared silently. I just checked that FF updated itself to 57.0.2. a) Did someone fix it already? This would be great! b) Maybe I unwittingly closed a tab that could have caused it? But since the tabs run in separate processes an "offending" tab should not be able to cause such behaviour, unless they depend upon shared resources. I installed the extension anyway (disabled), just in case anything of the kind happens again. Thanks for all help!
Flags: needinfo?(genesis)
Please reopen and provide the performance profile if you experience this again. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
FF 57.0.4 - Problem has not reappeared. Some tabs seem to take a long time to load, but it is not like the bug I reported. Keep up the good work! Thanks a lot for fixing all the bugs!
You need to log in before you can comment on or make changes to this bug.