- Home /
Unity 4.3 beta + MonoDevelop + Attach to process = crash
Has anyone else been having problems launching their game in editor after having attached to process in MonoDevelop to debug? Every time I hit play I get a crash. However, if I attach to the process while it's already playing it doesn't crash and I can debug. But as soon as I try restart or detach it crashes. Any ideas? Cheers, Paul
Answer by TimK.Disney · Sep 13, 2013 at 07:18 PM
This is a known problem with the experimental Unity debugger plugin for Xamarin, as well. You can work around it by waiting to attach the debugger until after you have hit play. However, you also have to detach before you stop playing, or it will crash. (Assuming it's the same crash... the symptoms sound very similar, but I'm not in the beta, personally, so I have no way to know for sure.)
The issue is the failure to allocate thread local storage in the mono runtime that Unity uses. I'm rather surprised this hasn't been fixed yet, since they announced they will support the new version of MonoDevelop in the release version of 4.3.
This still hasn't been corrected in 4.3 G$$anonymous$$. Any suggestions on how to fix it?
Unfortunately, no. As it's a core problem with the $$anonymous$$ono runtime that Unity is using, I'm pretty certain they have to fix it.
This is plaguing our office too. We're following what you've described as a workaround for the time being, but this definitely needs fixing!
I made a new scene + a new script to run and I placed some breakpoints in them and they were working fine.
I might be completely wrong, but our game is currently using SmartFox for our server tech and the crash only seems to happen in a file / scene that has SmartFox code in it.
Are you using any fancy libraries in your game? That could possibly be causing this. I know that doesn't help but it might be useful to know.