Everything is in the title.
- Having a piece of code that call WWW.Dispose() when a custom timeout has been reached
- Set a low bandwidth throttling in a proxy tool (Charles by example)
- Pass throught proxy with an Android device
- Launch, start to load something… your custom timeout is reached X seconds later, you call the Dispose method and the application freeze.
The app is responsive around 40-60 seconds later (when the real WWW timeout has been reached).
If I stop the throttling during the freeze, the app instantly resume.
This behaviour has been noticed 2+ years ago.
I’m using Unity 5.2.0f3 and I’m seriously considering using another development tool. In other words, quit Unity because of its lack of stability.