Description of problem: Occasionally I get the browser warning that "a script on this page is busy or not responding..." Most often I see script no 1, occasionally others like no 2: 1. https://translate.engineering.redhat.com/webtrans/codemirror-compressed.js:1 2. https://translate.engineering.redhat.com/webtrans/416E149374AC1C5769C28FCD53C21832.cache.html:4890 Version-Release number of selected component (if applicable): 2.0 How reproducible: sometimes Steps to Reproduce: 1. open project in editor 2. load new/next page in that document Actual results: Sometimes a script stops working when trying to change to a new page. Expected results: No warning Additional info: This is on FF 16
I should add that when simply clicking on "continue" instead of "stop script" on that warning, everything seems to keep working fine - new page loads, no issues.
May need to change firefox default timeout on scripts or switch to Chrome as a work around
It seems that I am experiencing same. Warning: Script not responded "The script of this page takes longer for processing or not responding. Choose to stop the script now or to continue. Script: https://translate.zanata.org/zanata/webtrans/codemirror-compressed.js:1" As Chrome is not default brower, I tried to install but failed.
When my CPU is busy doing other works (i.e. compiling code), even zimbra will give me this warning(I open zimbra in Firefox). It's common in javascript heavy site. If you are using firefox, please follow bellow link to adjust the setting. https://support.mozilla.org/en-US/kb/warning-unresponsive-script#w_letting-the-script-run-longer
Increasing the script timeout is a workaround, but if this is happening, it means our JavaScript is doing too much synchronous work all at once. We need to look at what happens synchronously when loading a new page, and find ways of breaking up the work. http://stackoverflow.com/a/2686177/14379 http://www.nczonline.net/blog/2009/01/13/speed-up-your-javascript-part-1/
I'm glad you say that, Sean. Also, I've tried the workaround and it effectively doesn't make a difference. I disabled the actual notifications a long time ago anyway, but the "freezing" (firefox window going grey) still happened. After changing the timeout value the behaviour hasn't changed, firefox still freezes for a few moments every time I load a new page (and sometimes on other occasions) Using Chrome/Chromium instead is no option.
I haven't been able to reproduce the timeout with Firebug running yet, but if RPC deserialisation is the problem, we might just have to make multiple smaller requests. If slow DOM manipulation is the problem, we might be able to use GWT's Scheduler.scheduleIncremental to help. But ultimately this may be unavoidable while we continue to use CodeMirror plus the current editor table based on Grid and Composite. http://stackoverflow.com/a/8760527/14379
I should add that this happens at other times, too, not only when loading a new page of the same document. It sometimes happens when going to a different tab in the browser (to research some term for my translation) and then going back to Zanata. It sometimes happens when pasting text into the editor. It sometimes happens when changing between search&replace and the editor. And it almost always happens when loading a new page. Overall this is a big performance problem, and during some tasks (e.g. proofreading, going back and forth between browser tabs and different documents on Zanata a lot) I find it slows me down a lot. BTW, my CPU is not busy doing anything else. Two browsers, Thunderbird and Xchat are running, that's usually it. Thanks for looking into it.
Hi Hedda. Have you experienced this issue recently?
Hi Damian, Can you help reproducing this bug to see if this is fixed or still an issue? Thanks.
I havent seen this happing in quite some time. :-)
Thanks Hedda. Closing per your feedback. If it happens again, feel free to re-open the bug.