Skip to content
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

High CPU usage in Firefox browser (19.0.2) running WebSocket (1.0.11) in jetty 8 server #964

Closed
harishalwala opened this issue Mar 18, 2013 · 5 comments

Comments

@harishalwala
Copy link

Hi

We are using GWT Atmosphere Websockets(1.0.11) on jetty 8 server.
In our application, Server would send the text send to client browsers using websockets. Application works fine in all browsers except in Firefox browser. Client running application in Firefox browser consumes high CPU while showing the text on the browser.

Any idea what could be the issue.

Earlier we had same issue in chrome also, but when we replaced old atmosphere jars (0.9.4) with new version 1.0.11, issue looks to be resolved.
Note : We are using GWT Atmosphere.

@jfarcand
Copy link
Member

@harishalwala you need to gives me more information about what is causing that and how to reproduce the issue. A test case would be really appreciated.

@jfarcand
Copy link
Member

Can you profile using Firebug the client side? That will gives you what is eating the CPU.

@harishalwala
Copy link
Author

I will check and let you know

@harishalwala
Copy link
Author

I have done the profiling using firebug in Firefox browser, it points to a method in third party js file. However since I am working with GWT application, I dont think there will be any help even if profiler shows issue in js file. Is there any other way to validate the issue.

@jfarcand
Copy link
Member

Hard to say....try to reduce the script at minimum, remove Atmosphere and see if you can pinpoint the issue (more details). Closing this issue as not a bug (in Atmosphere)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants