Bug 1320190 - [UI] web UI consume huge amount of RAM in firefox (on client machine)
Summary: [UI] web UI consume huge amount of RAM in firefox (on client machine)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: UI
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3
Assignee: Soumya Deb
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 14:32 UTC by Daniel Horák
Modified: 2017-03-23 04:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 04:11:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
firefox about:memory graph (205.95 KB, image/png)
2016-03-22 14:32 UTC, Daniel Horák 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1346003 0 unspecified CLOSED Unresponsive script 2021-02-22 00:41:40 UTC

Internal Links: 1346003

Description Daniel Horák 2016-03-22 14:32:54 UTC 
Created attachment 1139083 [details]
firefox about:memory graph

Description of problem:
  Sometime my browser (firefox) with opened USM web UI consume huge amount of RAM. 

Version-Release number of selected component (if applicable):
  rhscon-ui-0.0.23-1.el7.noarch
  rhscon-core-0.0.8-14.el7.x86_64
  rhscon-ceph-0.0.6-14.el7.x86_64
  
  firefox-41.0.1-2.fc23.x86_64

How reproducible:
  sometimes

Steps to Reproduce:
  I'm not aware of specific reproducer, but if I leave untouched firefox (special profile just for USM) with one or few opened tabs with USM UI, it consume huge amount of memory after a while (e.g. more than 3GB).

Actual results:
  The browser with opened USM web UI consume unreasonable huge amount of RAM.

Expected results:
  The browser with opened USM web UI consume reasonable amount of RAM.

Additional info:
  See the about:memory log in attachment, I'm not sure which other information I can provide to easily track this issue.
Note You need to log in before you can comment on or make changes to this bug.