Hide Forgot
Description of problem: High CPU utilization when the remote PC is slow to respond. CPU usage bounces up to 100%. Version-Release number of selected component (if applicable): remmina-0.7.5-3.fc14.i686 How reproducible: Always when the response of the remote system is slow either due to an hog or due to very slow connectivity. Steps to Reproduce: 1. Connect to a desktop (win o linux is the same) 2. Make it really unresponsive allowing for multi-second delays (make it swap intensively and most systems will slow to a crawl) 3. Notice how remmina uses 100% cpu while waiting for the client response Actual results: HiGH CPU usage probably do to some "busy wait" Expected results: Very low CPU usage since remmina should be waiting passively Additional info: I'm using a 32 bit OS
Can you try the latest version of remmina form http://repos.fedorapeople.org/repos/cwickert/remmina/ ?
I've used the new version of remmina for a while now (and BTW it is fantastic). though this particular problem is still there. A new problem (due probably to changes in ultravnc) is that the chat and "disable remote imput" do not work with the latest versions of ultravnc (1.8.5/1.8.6).
(In reply to comment #2) > I've used the new version of remmina for a while now (and BTW it is fantastic). > though this particular problem is still there. Confirmed, I just got another report in bug 715612. > A new problem (due probably to changes in ultravnc) is that the chat and > "disable remote imput" do not work with the latest versions of ultravnc > (1.8.5/1.8.6). I think both are extensions of UltraVNC that are not part of the VNC protocoll.
*** Bug 715612 has been marked as a duplicate of this bug. ***
> I think both are extensions of UltraVNC that are not part of the VNC protocoll. I concur. Chasing UltraVNC extensions to the VNC protocol is probably very hard, yet it would be fantastic to have those functions work with the current release too. P.s. I didn't really look at the remmina code, but indeed this might be more of an upstream problem, since remmina relies on libraries for VNC support.
As for VNC we need to upgrade libvncserver to 0.9.8. Currently F15 has 0.9.7 which is not officially supported by remmina. I am still about to coordinate the upgrade because it requries several rebuilds of other packages.
Yeah! And THAT is probably gonna be a pain... :( Doing packaging right can be a chore and that's why I'm so grateful to you guys who put all the effort in it. Thanks!!!
I use remmina to connect via RDP to Windows terminal servers, and see exactly this issue too. I normally trigger it when I am at home running RDP sessions, and then suspend and go to work. When I re-open, remmina immediately shoots up to 100% CPU - as obviously the old RDP sessions are not recoverable. I have to kill remmina to fix. So I'd guess that means it isn't related to the VNC code?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping