Comments
-
Eerk
An additional note that is possibly related: starting my computer definitely takes much (a minute or so) longer when Synergy is switched on at log-in. I tried restarting after switching off Synergy at log-in and the startup process was as expected.
-
Greg Hurrell
What's the effect of the setting (in the Advanced tab of the Synergy preferences), "Initiate connections to the Internet automatically when required (may cause Synergy to initiate a dial-up connection)"?
Is it on, or off? What happens when you switch it?
I am not looking at the source code right now, but from memory Synergy uses the SCNetworkCheckReachabilityByName API (or a similar one in the SCNetwork group) to check whether or not a host is reachable. The docs don't say anything about possible delays, but if the call to that API is causing the delay, I might have to move it into a separate thread.
Marking as ASSIGNED.
-
Eerk
Hello Wincent,
Thanks for the quick reply. The option "Initiate connections etc." is off. It is one of the options I mentioned I have switched off after quiting the album download (and therefore the internet connection).
Give me a minute...
I just did an interesting test: switching the internet connection off (with album artwork visible in the floater) is no problem untill I switch to a song that has _iTunes_ artwork connected to it. Switching back and forth between songs that have no or Synergy artwork connected, is no problem. Lag time is about 30 to 40 seconds before any response of Synergy comes back. When I switch the internet connection back on (because I wanted to send in this form) the response times are back to normal. Seems looking up (and finding) iTunes artwork causes this.
Hope this helps,
Eerk Hofmeester.
-
Eerk
Hello Wincent,
Yet another comment after testing further: this won't help I'm afraid, but the lag time also occurs with the album art switched off. Also my previous suggestion seems to be only half true. When switching to songs that have no iTunes artwork the lag can also occur. Only advantage is, is that my collection of Synergy artwork is growing steadily with all this on-line testing ;-)
Kind regards, Eerk Hofmeester.
-
Eerk
Just timed the lag time: it's exactly 60 seconds. Regards, Eerk.
-
Greg Hurrell
Ok. I believe I've fixed this. I am sending you a test build to your email address. Please let me know if it cures the problems.
There are two reasons why Synergy would connect to the net: (1) automatic version checking, and (2) Amazon searching. In the former case, Synergy first needs to know if the update host is reachable, and in the latter, whether xml.amazon.com is reachable.
I think the problem lay in the calls to the SCNetworkCheckReachabilityByName API. My interpretation of the docs was that if there was no net connection then the function would just return immediately and say "not reachable". But the fact that you see an exactly 60 second delay implies that it's getting up to some other mischief. Perhaps it's doing DNS lookups that are timing out or something.
In any case, I've done a bit of refactoring and moved the reachability checks for both situations (1) and (2) into separate threads. This means there should be no more delays.
Can you please test out the build? I will email it to you in a minute or two, after I've finished posting this comment. I'd like to know if it fixes the delays, if the "Initiate connections to the Internet automatically when required" checkbox works properly, and if your album cover downloads etc continue to work. I've done as much testing as I can here, and it seems to all work. But seeing as I never had the delays (I've got an always-on ADSL connection) I will only know for sure that it's fixed if you can confirm it for me.
-
Eerk
Hello Wincent,
Just received the build per e-mail. It's a little late now, but I will test it first thing when I startup my Mac again somewhere this weekend. Thanks for the quick work on this!
Regards, Eerk.
-
Eerk
Hello Wincent,
SUCCES! I installed 'my' 1.7.1 version and couldn't get it to lag, with or without a connection. Some additional artwork came in, so the connection (when available) is still used correctly. Just to be sure, I re-installed the original 1.7.1 version and sure enough, within seconds after going to a new song, the spinning beach ball was back. Installed the fixed 1.7.1 and all is well again. It seems your trick did it!
I think you can safely post 1.7.2 on the web.
Working with this version so intensely I came up with another wish for the list. I will post it in a separate thread.
Cheers and thanks a lot for your quick fix!
Eerk Hofmeester
-
Greg Hurrell
Excellent news. Glad to hear the fix works. Marked as FIXED.
-
Greg Hurrell
Marking as CLOSED.
Note to everyone else: If you're suffering from this bug and want to use the build that fixes it, you can pull it down.
MD5 checksum: e632d092a5dbaec849d98c5f877a525a
This is not an official release. It's identical in every way to the 1.7.1 release, apart from the fix. The fix will be officially released when 1.8 comes out (later this month, if my current schedule works out).
Add a comment
Comments are now closed for this issue.