davidebaldini
commented
9 years ago The Firefox profiler measures excessive script activity on the web console.
Attached to this post there are: graphical view of the profiler; json profiler output
Open davidebaldini opened 9 years ago
davidebaldini
commented
9 years ago The Firefox profiler measures excessive script activity on the web console.
Attached to this post there are: graphical view of the profiler; json profiler output
emmanuel-keller
commented
9 years ago Hi David,
The user interface of the current stable version of OpenSearchServer v1.5 is based on the Zkoss framework.
We made historically this choice because we wanted an RIA oriented user interface, without having to spend too much time on browser compatibility concerns.
Firefox and Iceweasel are brothers. The compatibility matrix is here (we are uzing ZK 6.5): http://www.zkoss.org/whyzk/Features
Do you get this bug on a specific part of the user interface ?
davidebaldini
commented
9 years ago Thank you for the comprehensive explanation. The overload is specifically triggered by accessing and subsequently leaving the tab: Crawler -> Web -> Crawl process
Only after leaving this tab, independently from the destination, the browser remains noticeably overloaded and firebug confirms this. I haven't tested further up to reaching a complete hangup.
I haven't tested on other browsers yet, except for this Iceweasel 31.
OSS version 1.5.11
I'm setting up an OSS instance on a dedicated server with sufficient hardware resources for the specific task. From a separate computer I access the remote OSS web console. After a few clicks thru the web console, the browser gets gradually more and more sluggish, eventually reaching a point of complete unresponsiveness.
Restarting the browser makes it temporarily responsive again.
Iceweasel 31 w/o plugins.
How can I inspect this problem more deeply?