Red Hat Bugzilla – Bug 1306261
[scale] - after prolonged use large memory growth in firefox
Last modified: 2016-03-16 03:29:55 EDT
Created attachment 1122781 [details]
Firefox Memory tree, growth over time, and raw mem report
Description of problem:
Firefox tab running ovirt becomes sluggish and non-responsive due to high memory use in firefox. Forcing user to close and re-open tab to improve sluggishness after prolonged use, which then re-occurs again.
-majority of memory contained by orphan nodes (530mb of total 1.1GB )
-memory growth of firefox process over time including effect of tab close shown
Version-Release number of selected component (if applicable):
Firefox version: 43.0.3
Takes some time to reproduce, and requires populated system.
30 ISCSI Data Domains
20 NFS Data Domains
1 VM pool of 15 VMs
1 VM pool of 20 Vms
Steps to Reproduce:
1. Browse through list of VMs wait 5-10 mins
2. Browse through list of storage domains wait 5-10 mins
3. Edit Storage or Vms, wait for 5-10 mins
4. Browse more though Vms/Domains
After 45 mins or so of intermittent use of browsing, editing storage domains, and vms the user experience becomes sluggish and hard to use. Memory growth should be detectable throughout use.
1 FF Tab is used, and must remain open for the duration of the test.
Meaning closing the tab, frees up memory.
See attachment, memory foot print high, user experience choppy, sluggish forcing user to close tab and re-log in for better experience.
Lower memory foot print, and no choppy/sluggishness after continued use.
Likely related to https://bugzilla.redhat.com/show_bug.cgi?id=1294678
Mordechai - can you test also 3.5?
Until you can verify that's a regression, this isn't urgent.
Please prioritize work of the scale team to test it in a real 3.5 environment.
*** This bug has been marked as a duplicate of bug 1294678 ***