Description of problem: Sometimes there is alert about unresponsive script, see screenshot. Version-Release number of selected component (if applicable): ceph-ansible-1.0.5-19.el7scon.noarch ceph-installer-1.0.11-1.el7scon.noarch rhscon-ceph-0.0.20-1.el7scon.x86_64 rhscon-core-0.0.21-1.el7scon.x86_64 rhscon-ui-0.0.34-1.el7scon.noarch How reproducible: hard to say Steps to Reproduce: 1. install Console and use UI Actual results: There is alert about unresponsive script. Expected results: There is no alert about unresponsive script.
Not reproducible. More info required
(In reply to Nishanth Thomas from comment #2) > Not reproducible. More info required Steps to Reproduce ================== 1. Start Firefox with a clean profile for usm testing only. 2. Install RHSC 2.0 following the documentation. 3. Use RHSC 2.0 web UI via Firefox for various tasks. How reproducible ================ I stumble upon this issue at least once a day. Additional Info =============== While this doesn't seem as a big issue at first sight, it may be caused by bigger internal issues. Moreover it definitely affects the user experience.
Additional Info: I use Firefox on Fedora for manual testing (current build is firefox-47.0-4.fc23.x86_64).
Per discussion in bug scrub meeting, moving this bug to ON_QA. When you see this issue again, need to have the firebug console logs, cpu/memory utilization. if it is an issue related to cpu/memory consumption, there another bug already raised for that.
Created attachment 1170653 [details] screenshot of "Script may be busy" notification I have noticed this issue today with rhscon-ui-0.0.39-1.el7scon.noarch attaching screenshot.
When this "Script may be busy" notification appeared, I did the following actions to get more details: * generated firefox memory report via about:memory * clicked on "Debug script" button of the warning and saved the logs from there (see attachments) Also moving back to ASSIGNED since the issue was reproduced.
Created attachment 1170688 [details] debug logs from firefox console
Additional info =============== When the notification is shown, Firefox uses about 30-50% of cpu, but when I click on continue, firefox cpu usage goes high up to 110% and the UI is not responsive at all until the warning about not responsive scripts appears again then, the cpu utilization of firefox is again on about 30%.
(In reply to Nishanth Thomas from comment #6) > need to have the firebug console logs, cpu/memory > utilization. if it is an issue related to cpu/memory consumption, there > another bug already raised for that Which firebug console logs do you have in mind? Since this is likely related to bloated/ineffective javascript code, logging http requests may not help. Moreover both firefox debugger and firebug console doesn't provide direct way to export current state of the javascript code running. Based on this, I believe that the most effective way to evaluate this issue is for you to reproduce and then you can use debugger yourself.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days