-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak in C3 charts when navigating on to and off of VM details #1031
Comments
Originally posted in #956 (comment) I tested Chrome 74.0 on Mac against the web-ui dev server and against web-ui installed to my dev ovirt-engine and was able to reproduce the c3 no charts problem and the browser tab crashing problem. The tab appears to crash because of a massive memory leak. I also tested with Firefox on fedora against my dev ovirt-engine with web-ui installed and recreated the memory leak there. Firefox's tab doesn't crash as politely as the Chrome tab. Here is a video of the Chrome 74.0 on Mac C3 fail followed by memory leak and tab crash: |
Originally posted in #956 (comment)
In my testing of this issue, I never had to change the running state of the VM. I only had to swap back and forth between the webvnc console and the VM details page. I doubt the VM's actual console or running state change has a direct impact on this issue. |
Logs from Dev Tools
|
@bond95 and I just sat to duplicate the issue and we were able to reproduce it consistently in current master (webvnc merged) and in the 1.5.2 release. The issue seems to be localized more around transitioning off of the VM dashboard details page. Web console exaserbates the problem by giving another easy path to transition off of the VM dashboard page. Steps to reproduce:
When the charts stop rendering, a memory leak has occurred. The app will continue to function until the c3 charts take too much memory and the browser kills the tab. |
@sjd78 is there a difference between browsers? |
The only tracker ovirt-web-ui is using is the github issues tracker |
@doron-fediuck It was tested only on Firefox and Chrome, and there is no difference, it can be reproduced in the same way. |
It seems I have the reproduction steps:
It doesn't happen 100%, but mostly. Reproduced in Google Chrome 74.0 and also Firefox 66.0
Originally posted by @leistnerova in #956 (comment)
The text was updated successfully, but these errors were encountered: