Application.Quit() causing build using rope to crash (Unity 2017.1.1)

[ContrarySchol]

Currently having issues with quitting based on the rope, where the build just hangs without closing properly, then transitions to not responding.

Documentation does not explicitly mention having to destroy the rope manually, is there something we're missing?
We've previously tried the system process killing method, but aren't sure about it as it has a reasonable chance to not actually close the process itself.

[josemendez]

Currently having issues with quitting based on the rope, where the build just hangs without closing properly, then transitions to not responding.

Documentation does not explicitly mention having to destroy the rope manually, is there something we're missing?
We've previously tried the system process killing method, but aren't sure about it as it has a reasonable chance to not actually close the process itself.

Hi there,


We discovered an issue in certain Win 7/8 machines where Obi's task manager was not properly destroyed upon program termination. This is due to a bug in MSVCPP that causes static member destructors to be ignored when unloading a .dll. In our case this caused worker threads to linger around even after Application.Quit() is called. It has been circumvented on our side and the fix will be released in the next update. 

Try replacing the /Obi/Assets/x86 and x86_64 folders with the patched ones you'll find here, that should fix the problem:
https://we.tl/kB3pYoWG3T

Let me know how it goes! cheers,

[ContrarySchol]

Hi there,


We discovered an issue in certain Win 7/8 machines where Obi's task manager was not properly destroyed upon program termination. This is due to a bug in MSVCPP that causes static member destructors to be ignored when unloading a .dll. In our case this caused worker threads to linger around even after Application.Quit() is called. It has been circumvented on our side and the fix will be released in the next update. 

Try replacing the /Obi/Assets/x86 and x86_64 folders with the patched ones you'll find here, that should fix the problem:
https://we.tl/kB3pYoWG3T

Let me know how it goes! cheers,

We're all good now Jose, thanks for the files