Closed
Bug 542217
Opened 16 years ago
Closed 15 years ago
Firefox goes into a hang (50% CPU) when connecting to the Omnis Web Client plugin
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: support, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
759.48 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 GTB6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6
We would like to report what we consider to be a major issue with this release of Firefox 3.6 on the Windows 32Bit platforms (XP/Vista/7 and possibly others).
As far as we can see, this is not a problem for the Mac OS X platforms.
This version is causing problems with our Omnis Web Client Plugin (see note*) (NPH-OmnisCGI.exe) for clients that have upgraded to this version of Firefox – there have been and there are still no issues with previous versions of Firefox (3.2.x, 3.5.x).
From what we have established, as soon as you click on something within our plugin that sends an event to the server, Firefox enters a tight loop (see Task Manager and Firefox CPU usage will be at 50% or higher).
It is only when the mouse leaves our plugin that Firefox starts to receive the response from the client (even though it was sent immediately).
We can see that the Omnis Web Plugin is not in a tight loop within our code, so it looks as if this is a Firefox 3.6 issue, particularly as this still works for previous versions of Firefox.
This problem can be demonstrated very simply by downloading and installing the Omnis Web Client plugin and then testing some simple examples that are currently available on our Web site.
You can download the ‘Web Client plug-in version 5’ from the following URL (http://www.omnis.net/download/index.html), and then run the downloaded application Omweb.exe, for which you will require Administrative permissions.
The application will install the necessary components depending on the platform to, c:\Webclient for Windows XP, or to C:\Users\xxxxxx\AppData\LocalLow\TigerLogic\webclient for Windows Vista/2008/7
Also, an Environment Variable (MOZ_PLUGIN_PATH) will be created, which will contain the installed path of the Web Client plugin.
After having downloaded and installed the Web Client plugin, it will be necessary to re-start the PC.
You can then use Firefox to access the Omnis Web Client Gallery and test the examples (http://www.omnis.net/products/webclient/index.html?detail=gallery).
If you start with the Books example, the example will be displayed immediately within the browser, but when clicking any of the objects (push buttons, sidebar icons.etc), very little will happen and the task manager will show Firefox at 50% CPU usage.
Moving the cursor out of the browser (plugin area) will then release whatever loop Firefox is in, and the web page will the display correctly.
Likewise, if you try the Images example, nothing will occur until you move the cursor out of the browser (plugin area). Again, the Task Manager would be showing that Firefox was using 50% of the CPU.
Note: * The Omnis Web Client Plugin is proprietary to TigerLogic Corporation (http://www.omnis.net/products/webclient/index.html)
Reproducible: Always
Steps to Reproduce:
1.Download and install the Omnis Web Client Plugin as described above
2.Test the two examples as described above
3.
Actual Results:
See explanation in Details section
This will affect many of our end users.
Should the need arise, please contact us at the email address 'Support@omnis.net'
Comment 2•16 years ago
|
||
the behavior is confirmed by bug 542197, can't tell on which side is the failure, but worth investigating, so confirming.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a2pre) Gecko/20100211 Minefield/3.7a2pre
This appears to work fine now using the latest nightly. This screenshot proves the performance.
Resolving WORKSFORME. If you can reproduce the issue with the latest nightly, please reopen and provide details about how you reproduced it.
Thanks!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•