Bug 471259
| Summary: | With latest testing updates, synergy uses all available cpu | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> | ||||
| Component: | synergy | Assignee: | Matthias Saou <matthias> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 9 | CC: | farrellj, gilboad, matthias, stig-redhat-bugzilla | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 1.3.1-12.fc10 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-03-09 22:45:29 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
I can reproduce this. 1) on server: synergys 2) on client: "synergyc server" 3) reboot client after connected 4) notice synergys cpu usage is 100% (sometimes you have to move the mouse around violently to see the cpu spike; sometimes not) 5) when client is booted back up, start "synergyc server" again 6) when it reconnects, synergys cpu usage goes back down Does downgrading to 1.3.1-9 fix this particular issue? Yes. FYI - I'm on F10 now and see the same (-10 sucks CPU, -9 doesn't). Created attachment 332889 [details]
Fix so that infinite timeout (dtimeout < 0.0) is handled correctly
I have the same problem with 100% CPU time in the server and my synergy client can't connect to the server. It looks like the stuttered-delay-fix patch didn't correctly handle the case when CXWindowsEventQueueBuffer::waitForEvent() is called with a negative value. The caller then appears to expect an infinite timeout, but instead got an immediate timeout with no calls to select()/poll(). The attached patch fixes this and makes it possible for me to use synergys on a fedora 10 system.
Thanks a lot for tracking the problem down and providing a patch! I'll test it and prepare updates-testing packages which include it. synergy-1.3.1-12.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/synergy-1.3.1-12.fc10 synergy-1.3.1-12.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/synergy-1.3.1-12.fc9 synergy-1.3.1-12.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing-newkey update synergy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-2159 synergy-1.3.1-12.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update synergy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-2151 i was having the same problem with synergy -10 and downgrading to -9 fixed it... upgrading to -12 also seems fine, but -10 is absolutely screwed up so push the new version out into the world... I can confirm that -12 solves the problem. Thanks! - Gilboa synergy-1.3.1-12.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. synergy-1.3.1-12.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: I'm running with updates-testing enabled. Last night I pulled in synergy-1.3.1-10.fc9, kernel-2.6.27.5-32.fc9.i686 and kde 4.1.3. Now synergys consumes all available cpu. strace shows: [pid 6189] gettimeofday({1226510957, 98066}, NULL) = 0 [pid 6189] read(3, 0x8f1832c, 4096) = -1 EAGAIN (Resource temporarily unavailable) [pid 6189] gettimeofday({1226510957, 98217}, NULL) = 0 [pid 6189] read(3, 0x8f1832c, 4096) = -1 EAGAIN (Resource temporarily^C <unfinished ..> Version-Release number of selected component (if applicable): synergy-1.3.1-10.fc9.i386 How reproducible: everytime