http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo

Looking forward to the fix, really makes some pain.

As a workaround, you can dispose www in another thread.

private void DisposeWWWInBackground (WWW www)
{
new Thread( () => {
Debug.Log("WWW dispose started in background thread.");
www.Dispose();
Debug.Log("WWW dispose finished.");
}).Start();
}

Any workaround for this now?

We are also seeing this same bug. We start a co-routine with this code:

WWW www = new WWW(url, System.Text.Encoding.UTF8.GetBytes(postJSONText), postHeader);
bool hasTimeLeft = true;
while (!www.isDone && hasTimeLeft)
{
yield return null;
hasTimeLeft = Time.realtimeSinceStartup <= startTime + _waitForDownloadSeconds;
}
if (hasTimeLeft) //We didn't time out!
{
//Do some stuff.
}
www.Dispose();

If the internet is slow and _waitForDownloadSeconds occurs before WWW.isDone the game freezes.