- Home /
Problem with Application.Quit and Async networking
Hello, I am currently creating an application using Unity that makes heavy usage of some built in C# Async callback features, specifically for networking.
For some reason though, even when I call Application.Quit, the component continues updating and the Quit does not occur. Is there any way to figure out exactly what is preventing the Application from quitting?
I have verified that all my sockets are closed/shutdown/nullified before calling quit, but I am assuming that there are still threads alive with pending operations.
I have been using a "delegate" based approach but if there is a workaround using thread-pools or another method, I would be happy to try this. Even a way to determine what is preventing the quit would be extremely helpful.
Would it help to try to "Destroy" the Networking component?
Thanks in advance!
Your answer
Follow this Question
Related Questions
Loading Progress using UNET 2 Answers
Unity networking tutorial? 6 Answers
Async execution with blocking methods 0 Answers
Unity Asynchronous Socket Client - Threading Problem 2 Answers
Switch Levels with Async and still display progress 2 Answers