Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1336797 - RHEVM connections randomly report Error: A Request to the Server failed: (Error): Not enough storage is available to complete this operation. using IE 11
RHEVM connections randomly report Error: A Request to the Server failed: (Err...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.5.7
Unspecified Unspecified
high Severity low
: ovirt-4.0.0-rc
: 4.0.0
Assigned To: Greg Sheremeta
Petr Matyáš
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-17 09:11 EDT by Frank DeLorey
Modified: 2017-03-27 10:56 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-08-23 16:39:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: UX
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1743 normal SHIPPED_LIVE Red Hat Virtualization Manager 4.0 GA Enhancement (ovirt-engine) 2016-09-02 17:54:01 EDT

  None (edit)
Comment 7 Greg Sheremeta 2016-06-02 14:55:56 EDT
This is a memory leak issue. Although we see the issue here in IE11, other browsers should theoretically have similar memory / performance issues on 3.5.z.

I was able to reproduce the issue in oVirt 3.5.8, with 200 hosts, using IE11 and idling on the hosts tab for 15 minutes. Memory profile in IE showed a relatively high amount of memory leaking (1.4 GB in 9 minutes). 

I then mimicked that setup in 4.0-master, also with 200 hosts. In IE11 and idling for 30 minutes, I could not reproduce the issue. Memory profile showed way less memory burn than 3.5.8.

I then applied a patch from Bug 1294678 to 3.5.8, thinking that that was such a large leak that maybe this patch alone would help. But I still got the error popup with that patch applied. Thus, I suspect there have been several frontend memory improvements between 3.5.8 and 4.0.

I did not do any testing on 3.6. For reference, 3.6.5 has the patch from Bug 1294678 applied, and has other memory improvements.

My recommendation for now would be to mark this as fixed in 4.0, and possibly fixed in 3.6.5 too.
Comment 8 Greg Sheremeta 2016-06-03 15:12:22 EDT
We decided to test this out on 3.6.7.

In 3.6.7, memory is leaking worse than in 4.0, but not as bad as in 3.5.8. In IE11, I idled for 30 minutes and did not receive the error popup. However, after 30 minutes, the performance of the UI was sluggish. 900MB of memory was used, which is high in my setup.

Using Chrome 49 on the same 3.6.7 setup, and also idling for 30 minutes, I didn't receive an error popup, nor did the UI become sluggish.

Based on this, I conclude that 4.0 has better memory usage and will work better for IE11 users.
Comment 9 Petr Matyáš 2016-06-30 09:11:43 EDT
Verified on 4.0.0-19 on Win7 64b with IE11
Comment 11 errata-xmlrpc 2016-08-23 16:39:51 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1743.html

Note You need to log in before you can comment on or make changes to this bug.