Unity standalone build only works if Script Debugging flag is set

First, a bit of background. Some time ago, a couple of games made Unity just stopped working on my machine all of sudden. I did a bit of investigation recently and managed to conclude that it was an issue in Unity. So I downloaded the editor and tried to build and run the example project (AngryBots). And lo and behold, I have the exact same type of issue when I try to run the project as a standalone build.

The error is that the player creates the window but the process immediately hangs up and has to be killed via task manager. The output.log does not show any kind of error, is just stops writing. But the funny thing is... if a build the same project as a Development Build with the ScriptDebbuging flag enabled, the game works completely fine! If the Script Debugging is off, the same error occurs again (even if it is a development build).

I'm on Windows XP SP3 with everything up to date. Does anybody has any idea what's going on?

 

So, nobody has any idea what could be going on?

I did some more tests and found that what allows the build to work is a mysterious "PlayerConnectionConfigFile" file located in the data folder. I searched for info about it but didn't find anything. What's interesting is that the same file is present in the dev only build. If I edit some of the values and set them to 1, the dev build also starts working. But unfortunately, this doesn't work for the non-dev build... I guess the player doesn't even check this file

 

I experience the same issue. My game is just working if the ScriptDebugging flag is set. Has anyone found a solution or at least an explanation?

 

Got sort of the same issue today. In the editor or if I enable Debug build in standalone it runs fine. A standalone build without Debug flag somehow changes calculation so a while-loop in my code runs infinite. Tried to debug that with the glorious Reporter console tool for a while, but without success till now...