when I pressd the play button, once there is no internet, the editor would crash, and no error window shows. I go to the log folder to find the editor log, and the last line is :
Assertion at …\mono\metadata\threads.c:1788, condition internal not met.
I tried to reinstall the unity3d 2019 2.11f,and useless. I created a new project, and still crash when there is no internet.
and if build the project, the exe file is working fine.
Just a quick note to say that the Unity support team got in touch with me today to say that:
“I have forwarded the issue to the developers responsible for this area and I will let you know any findings as soon as possible”.
I just got this issue today and it’s been a wild ride trying to get to the bottom of it. I think it’s occurring from a Resources.LoadAll call because I managed to trip across a line that, if commented out, gets the play function to work but the game comes up paused so it’s not 100% good. Plus… I sorta heavily rely on that loadall call so I can’t think of a workaround yet.
You mention that not having internet is the cause, but I am connected to the internet. However, I saw this error earlier today before the play-button crashes began:
error:00000000:lib(0):func(0):reason(0)Curl error 35: Handshake did not perform verification. UnityTls error code: 7
error:00000000:lib(0):func(0):reason(0)Curl error 35: Handshake did not perform verification. UnityTls error code: 7 (Filename: C:\buildslave\unity\build\Modules/UnityWebRequest/Implementations/TransportCurl.cpp Line: 734) * Assertion at …\mono\metadata\threads.c:1788, condition `internal’ not met
I’m not using Resources.LoadAll, but I am using Resources.Load in various places (and I’m connected to the Internet) so it could be similar. The weird thing is everything was working fine last night, and then without making any changes it started crashing today.
I tried a complete clean install of Unity (deleted every version I had, preferences, the Hub, etc.) and tried on both 2019.2.12 and 2019.2.14 but still got the error. Hoping it really does get fixed with the next release.
Same here. Worked fine last night. Zero changes made. Run Unity this morning and this shit starts happening. I’ve actually had Unity run by commenting out the Resource Load calls, then uncommenting them, which is just… really stupidly broken… the issue then occurs in a coroutine call which causes the crash… then the crash keeps happening after commenting THAT call out while ALSO commenting out the resource load calls. It’s freaking WILD how broken Unity got today!
My project works fine on another computer. I’m too scared to completely clean Unity off considering this should be fixed in the next release.
How often does Unity release because I need this work done by uhhh next week and I’d very much like to not have to develop on my second machine.
To those interested in an update on the original issue (editor crashing when there’s no internet connectivity), the latest from the Unity support team is that they expect it fixed in 2019.2.16f1.
Hi, same here.
Editor 2019.2.13f1 crashes without any warning, anytime I try to access an invalid url on a UnityWebRequest or even through a Playfab API request.