-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
EXC_BAD_ACCESS when using IPC on OS X #417
Comments
It looks like in |
Interesting... I wonder why it crahsed... and why unlocking the mutex later fixes the issue :D I'll test this on my side and let you know. Thanks for the feedback anyway (and for the patch). |
|
Well, with your patch it crashes on my side (Windows,Qt 5.6 and Visual Studio 2013). I agree that it probably masks something else. The mutex is just here to protect the few members of the class. Therefore there's no reason to leave it locked after having modified them (the next calls are made to native Qt methods only, therefore the class members won't be read or write). Anyway I updated the code to make it much simpler (with Qt 5 we can more easily use QAtomicInt instead of int values, etc.). Can you tell me if it fixes your issue? P.S.: Here is the longer story:
|
Yes, this fixes the problem I was seeing. Thanks for the Qt education also. Why wouldn't you use Genuinly curions, not busting on you. |
Yes, since version 2.7 we are now using c++11 compiles only... But I need to get used to it ;) |
Running 10.12 Beta, Apple LLVM version 7.3.0, Qt 5.7 installed with native installer, building under CLion in Debug mode. CloudCompare is consistently on crashing on trunk in ccProgressDialog. I've attached the data files, Rock1 is the model, Rock2 is the data. Running with default parameters it crashes quickly, when reducing the final overlap (25%), it runs for longer or succeeds in the mapping, but still fails more often than not.
I had the same problem running Qt 5.6.1 installed with MacPorts
Running with 25% final overlap.
rocks.tar.zip
The text was updated successfully, but these errors were encountered: