Comments
-
Greg Hurrell
Thanks very much for the report, Barry. I will take a look at the code that's in the stack trace you've posted, but in the meantime can you try one thing for me: delete the Synergy preferences file, or temporarily move it out of the way. You should find it at:
~/Library/Preferences/org.wincent.Synergy.plist
It would be could to rule out possible preferences file corruption as a cause.
-
Barry Fishman
Hi Wincent --
You're welcome. I just did as you asked, and the application still crashes on launch (without creating a new preferences file, BTW). As a side note, when I was getting repeated crashes earlier, I clicked the "reset and relaunch" option, which I believe wipes out preference files.
By the way -- you might want to include instructions on how to properly remove 3.5a2 or earlier to the ReadMe for 3.5a3, or note if no special removal instructions are needed.
-Barry
-
Greg Hurrell
(In reply to comment #2)
You're welcome. I just did as you asked, and the application still crashes on launch (without creating a new preferences file, BTW). As a side note, when I was getting repeated crashes earlier, I clicked the "reset and relaunch" option, which I believe wipes out preference files.
Ok I've started analyzing the code in question, and I can see there are a coupleof logging statements in that code path. Can you look in the system log using the /Applications/Console.app? See if anything helpful there is printed? Specific candidates which might have cropped up could mention LSSharedFileListItemResolve or CFURLGetFileSystemRepresentation.
By the way -- you might want to include instructions on how to properly remove 3.5a2 or earlier to the ReadMe for 3.5a3, or note if no special removal instructions are needed.
Ok, will update the README. No special removal should be needed because if an old version is present on the system the new version should throw up a sheet and offer to remove it for you.
-
Greg Hurrell
I've just made a change that should hopefully suppress the crash:
Note that this is merely trying to *avoid* the crash; we still need to find the underlying cause.
As I type this I'm waiting for a new nightly build to finish building and uploading which includes the above fix if you want to try it out. I am particularly interesting in two things:
1. Does it fix the crash at launch?
2. Do the "Launch at login" preferences work properly? (The change I've made above basically aborts the update of the login items if an unexpected nil value is encountered; so it might mean that the preference won't work properly. As I mention above, I still need to find out *why* we're getting that nil value).
Anyway, you can find out more about the nightlies in general here:
https://wincent.dev/s/nightlies/
And this is the URL of the nightly that I just finished uploading:
https://wincent.dev/a/about/wincent/weblog/nightlog/archives/2008/01/synergy_revision_9848c4f.php
-
Barry Fishman
I will take a look at the nightly build you just put up and let you know what happens. I'll also try re-starting to test the launch at login feature (though that feature has always worked for me in 3.5a2).
I'm not sure if you still want the console log messages, but here are ones that might be related to the 3.5a3 crash:
1/7/08 4:57:59 PM Synergy Preferences[1212] Error: LSSharedFileListItemResolve returned error -43 1/7/08 4:57:59 PM Synergy Preferences[1212] An uncaught exception was raised
1/7/08 4:57:59 PM Synergy Preferences[1212] *** -[NSCFArray insertObject:atIndex:]: attempt to insert nil 1/7/08 4:57:59 PM Synergy Preferences[1212] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFArray insertObject:atIndex:]: attempt to insert nil' 1/7/08 4:57:59 PM Synergy Preferences[1212] Stack: (
2465346155, 2428862619, 2465345611, 2465345674, 2417093008, 2416172548, 2416172308, 18223, 17687, 17827, 14706, 15160, 2465405557, 2441368942, 2441328540, 2441326845, 2441325888, 2441325694, 2441324846, 10286
)
1/7/08 4:58:07 PM com.apple.launchd[74] ([0x0-0x10c10c].com.wincent.SynergyPreferences[1212]) Exited abnormally: Trace/BPT trap
-
Barry Fishman
Good news to report: 3.5a3+(9848c4f) launches just fine on my machine, and also "launches at login" with no trouble.
So the workaround, at least, works!
-Barry
-
Greg Hurrell
(In reply to comment #5)
I'm not sure if you still want the console log messages, but here are ones that might be related to the 3.5a3 crash:
1/7/08 4:57:59 PM Synergy Preferences[1212] Error: LSSharedFileListItemResolve returned error -43
Excellent. That pinpoints the exact location where the problem is occurring. Now the only question is *why*. The function call which is unexpectedly failing is supposed to take a reference to an item in your login items and return the corresponding FSRef or CFURLRef (a reference to the item on disk).
My guess is that this is failing because there is an old item in your login items which is no longer present on the disk or has been moved, so the function fails. Can you take a look in your login items and see if there are any stale-looking items? (System Preferences -> Accounts pane -> Login items)
Looking at the headers, I see that error code -43 is fnfErr ("File not found"), so that's almost certainly what's happening. The fix I applied to the nightly last night is basically the correct course of action in this case, I think. Thanks for your help in troubleshooting this.
-
Greg Hurrell
Adding the "fixed-in-prerelease" keyword. As this is a potential crasher, will cut a new release within the next day or two so that people can get their hands on the fix (although I suspect that the number of affected people will be small, seeing as this depends on the login items being in a certain state).
-
Greg Hurrell
Ok, 3.5a4 is out, so will mark this as FIXED/CLOSED.
https://wincent.dev/a/products/synergy-classic/download/
https://wincent.dev/a/products/synergy-classic/history/#3.5a4
-
Barry Fishman
FYI: I think that I did find a "stale" login item, related to the Blue Harvest preference pane (cleans .ds files from servers and memory sticks).
I know this is closed, but let me just share with you some Console log entries from 3.5a4 that may be of interest. These occur upon launch of Synergy Preferences, and then when the sender changes to simply "Synergy" I have just clicked "Start".
1/8/08 7:55:06 AM Synergy Preferences[905] Error loading /Library/InputManagers/Smart Crash Reports/Smart Crash Reports.bundle/Contents/MacOS/Smart Crash Reports: dlopen(/Library/InputManagers/Smart Crash Reports/Smart Crash Reports.bundle/Contents/MacOS/Smart Crash Reports, 265): no suitable image found. Did find:
/Library/InputManagers/Smart Crash Reports/Smart Crash Reports.bundle/Contents/MacOS/Smart Crash Reports: GC capability mismatch
1/8/08 7:55:06 AM Synergy Preferences[905] Error loading /Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader: dlopen(/Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader, 265): no suitable image found. Did find:
/Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader: GC capability mismatch
1/8/08 7:55:06 AM Synergy Preferences[905] Error loading /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock: dlopen(/Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock, 265): no suitable image found. Did find:
/Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock: GC capability mismatch
1/8/08 7:55:07 AM Synergy Preferences[905] Error loading /Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher: dlopen(/Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher, 262): no suitable image found. Did find:
/Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher: GC capability mismatch
1/8/08 7:55:07 AM Synergy Preferences[905] Error loading /Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher: dlopen(/Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher, 262): no suitable image found. Did find:
/Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher: GC capability mismatch
1/8/08 7:55:07 AM Synergy Preferences[905] Error loading /Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher: dlopen(/Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher, 262): no suitable image found. Did find:
/Users/fishman/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X.bundle/Contents/Resources/Carbon Patcher.bundle/Contents/MacOS/Carbon Patcher: GC capability mismatch
1/8/08 7:55:07 AM Synergy Preferences[905] Couldn't find patch entry point 1/8/08 7:55:11 AM Synergy[906] Error loading /Library/QuickTime/LiveType.component/Contents/MacOS/LiveType: dlopen(/Library/QuickTime/LiveType.component/Contents/MacOS/LiveType, 262): Library not loaded: /System/Library/PrivateFrameworks/LiveType.framework/Versions/A/LiveType
Referenced from: /Library/QuickTime/LiveType.component/Contents/MacOS/LiveType Reason: no suitable image found. Did find: /System/Library/PrivateFrameworks/LiveType.framework/Versions/A/LiveType: GC capability mismatch
1/8/08 7:55:14 AM Synergy[906] Error loading /Library/InputManagers/Smart Crash Reports/Smart Crash Reports.bundle/Contents/MacOS/Smart Crash Reports: dlopen(/Library/InputManagers/Smart Crash Reports/Smart Crash Reports.bundle/Contents/MacOS/Smart Crash Reports, 265): no suitable image found. Did find:
/Library/InputManagers/Smart Crash Reports/Smart Crash Reports.bundle/Contents/MacOS/Smart Crash Reports: GC capability mismatch
1/8/08 7:55:14 AM Synergy[906] Error loading /Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader: dlopen(/Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader, 265): no suitable image found. Did find:
/Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader: GC capability mismatch
1/8/08 7:55:14 AM Synergy[906] Error loading /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock: dlopen(/Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock, 265): no suitable image found. Did find:
/Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock: GC capability mismatch
-
Greg Hurrell
(In reply to comment #10)
I know this is closed, but let me just share with you some Console log entries from 3.5a4 that may be of interest. These occur upon launch of Synergy Preferences, and then when the sender changes to simply "Synergy" I have just clicked "Start".
All those console messages are being emitted because you have some add-ons which are trying to insert themselves into Synergy, but failing to do so because Synergy uses Leopard's Garbage Collection and they do not. That's what all the "GC capability mismatch" messages are about.
Quickly scanning, looks like the things we're talking about are:
- Smart Crash Reports - Ecamm Plugin Loader - SafariBlock - Default Folder X - QuickTime/LiveType
Unfortunately there's nothing I can do to suppress those messages; they're not being emitted by Synergy itself despite the log message prefixes you're seeing. The reason I can't suppress this is that Synergy isn't the one loading these modules, rather the modules are themselves trying to insert themselves into Synergy's address space (and that of every other application you launch on the system). Basically, the messages will go away when the vendors of those modules update them to support Garbage Collection for Leopard.
-
Barry Fishman
Excellent -- thanks for the explanation! And I am glad that I was able to be helpful to you, thanks for the excellent software!
-B
Add a comment
Comments are now closed for this issue.