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

Problem with cmissync on Mac - crashes after 10 seconds #732

Closed
ianw1974 opened this issue Nov 25, 2016 · 11 comments
Closed

Problem with cmissync on Mac - crashes after 10 seconds #732

ianw1974 opened this issue Nov 25, 2016 · 11 comments

Comments

@ianw1974
Copy link

Hi,

We have a new install of cmissync on macOS Sierra 10.12.2 and cmissync version 2.4.9.0. Cmissync opens fine, but then after 10 seconds or so, it closes. We cannot even add a remote folder because it closes before we get chance to finish.

Attached log file.
cmissync.txt

@ianw1974
Copy link
Author

Also we have tried on another Mac with 10.12.1 and the problem also occurs.

@khoran
Copy link

khoran commented Feb 7, 2017

I'm having the exact same problem on mac OS sierra 10.12.3. CimisSync version 2.4.9.0. The service runs ok, when I try to add a remote folder, it just closes after about 10 or 20 seconds.

Here is a log excerpt:

2017-02-07 10:29:16,608 [1] INFO  CmisSync.Program [(null)] - Starting. Version: 2.4.9.0
2017-02-07 10:29:16,624 [1] INFO  CmisSync.Lib.FolderLock [(null)] - Creating folder lock file: /Users/dalerickards/CmisSync
2017-02-07 10:29:16,720 [1] DEBUG CmisSync.SetupController [(null)] - SetupController - Entering constructor.
2017-02-07 10:29:16,721 [1] DEBUG CmisSync.SetupController [(null)] - SetupController - Exiting constructor.
2017-02-07 10:29:16,937 [3] DEBUG CmisSync.StatusIcon [(null)] - StatusIcon UpdateIconEvent 0
2017-02-07 10:29:16,943 [3] DEBUG CmisSync.StatusIcon [(null)] - StatusIcon UpdateIconEvent 0
2017-02-07 10:31:44,540 [1] FATAL CmisSync.Program [(null)] - Exception in Program.Main
System.MethodAccessException: Method `(wrapper dynamic-method) object:[MonoMac.Foundation.NSObject+NSObject_Disposer:Void Drain(MonoMac.Foundation.NSObject)] (intptr,MonoMac.ObjCRuntime.Selector,MonoMac.Foundation.NSObject)' is inaccessible from method `MonoMac.Foundation.NSObject/NSObject_Disposer:Drain (MonoMac.Foundation.NSObject)'

  at (wrapper managed-to-native) MonoMac.AppKit.NSApplication:NSApplicationMain (int,string[])
  at MonoMac.AppKit.NSApplication.Main (System.String[] args) [0x0003d] in <71d47765320247af8e47b4cb89fa9e28>:0 
  at CmisSync.GUI.Run () [0x00001] in <927d8382543f447e8b0c18a2bde05555>:0 
  at CmisSync.Program.Main (System.String[] args) [0x001c5] in <927d8382543f447e8b0c18a2bde05555>:0 
2017-02-07 10:34:51,729 [1] INFO  CmisSync.Program [(null)] - Starting. Version: 2.4.9.0
2017-02-07 10:34:51,743 [1] INFO  CmisSync.Lib.FolderLock [(null)] - Creating folder lock file: /Users/dalerickards/CmisSync
2017-02-07 10:34:51,859 [1] DEBUG CmisSync.SetupController [(null)] - SetupController - Entering constructor.
2017-02-07 10:34:51,860 [1] DEBUG CmisSync.SetupController [(null)] - SetupController - Exiting constructor.
2017-02-07 10:34:52,118 [3] DEBUG CmisSync.StatusIcon [(null)] - StatusIcon UpdateIconEvent 0
2017-02-07 10:34:52,124 [3] DEBUG CmisSync.StatusIcon [(null)] - StatusIcon UpdateIconEvent 0

@ArnoLP
Copy link

ArnoLP commented Feb 22, 2017

Hi,

I have currently the same problem. Mac OS 10.11.6. Version: 2.4.9.0

@ianw1974
Copy link
Author

Seems nobody is monitoring or fixing it. 3 months and no updates from the developer.

@mathieuga
Copy link

I found a tip in this link: https://forums.xamarin.com/discussion/78138/application-fails-on-launch-now-with-4-6-0-245-system-methodaccessexception

So may be until the update of cimssync you can try to install an new (older such as 4.4.2.4) version of mono (http://www.mono-project.com/download/)

@nicolas-raoul
Copy link
Contributor

We would love to fix this! Unfortunately all of our developers are busy with paying customers and other projects :-/
We have to prioritize tasks, and the Mac version being in beta, it is towards the bottom of a long list of things to do.
The good thing is that CmisSync is open source, so if anyone is motivated enough they might want to hire a developer to fix it? Or even fix it themselves?
Sorry for the inconvenience, and thank you for your comprehension!
Nicolas

@nicolas-raoul
Copy link
Contributor

Thanks @mathieuga for the tip!
All other tips and element of information that might lead to this bug getting fixed are very welcome, of course :-)

@ianw1974
Copy link
Author

We would have purchased cmissync but since it didnt work and that nobody replied it looks like that nobody is interested in fixing the problem to attract us to purchase it and want us as a client.

@bitwerkstatt
Copy link

bitwerkstatt commented Jan 5, 2018

@nicolas-raoul Does the recent adding of labels mean that there is any movement in this issue? We would love to use CmisSync with a new and renowned client (who would even pay for it :-) )

@nicolas-raoul
Copy link
Contributor

nicolas-raoul commented Jan 5, 2018 via email

@bitwerkstatt
Copy link

Was afraid you would say that. Thanks for the quick response.

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

6 participants