Windows terminates threads before the queue threads and other resources are released. This causes deadlocks with the condition_variables in the async_queue objects. This is a bug in Visual Studio/Windows that is documented here: https://connect.microsoft.com/VisualStudio/feedback/details/747145 This will leak some resources but these resources will be released by the operating system on exit.
umar456 added a commit that referenced this pull request
Sep 10, 2017
On Windows the resources that are released after the main function have exited cause "Pure Virtual Function Called" errors. It seems that Windows releases all resources when exiting main without calling their destructors. When the destructors are called this error is thrown. This is related to #1899
Merged
umar456 added a commit that referenced this pull request
Sep 10, 2017
On Windows the resources that are released after the main function have exited cause "Pure Virtual Function Called" errors. It seems that Windows releases all resources when exiting main without calling their destructors. When the destructors are called this error is thrown. This is related to #1899
umar456 added a commit to umar456/arrayfire that referenced this pull request
Sep 10, 2017
On Windows the resources that are released after the main function have exited cause "Pure Virtual Function Called" errors. It seems that Windows releases all resources when exiting main without calling their destructors. When the destructors are called this error is thrown. This is related to arrayfire#1899
Merged
umar456 added a commit that referenced this pull request
Sep 10, 2017
On Windows the resources that are released after the main function have exited cause "Pure Virtual Function Called" errors. It seems that Windows releases all resources when exiting main without calling their destructors. When the destructors are called this error is thrown. This is related to #1899
Closed