I’m running the 4.6 runtime, and I’m seeing pretty frequent crashes when I enter play mode. It doesn’t happen the first time I enter playmode, but it’s pretty consistent after 5-10 times. It might be that it relates to how long I’ve had the editor open, I don’t know though.
I upgraded from 2017.1.0f1 to 2017.1.0p4, and it seems to be happening more frequently.
The bug report was returned as a duplicate of this one. Does any of you working on this have any idea about what it is, or if there’s any way I can mitigate it?
I don’t have any details about how to mitigate it yet, but this one is on the top of our list to investigate, so hopefully we’ll have more details in a day or two.
I don’t think there will be a 2017.1.0p6, actually. It looks like we will have a 2017.1.1p1 though, which should have a number of crash fixes. Unfortunately, there is not an easy to build Mono your self in the way we use it. We have a pretty highly customized version of Mono.
We’re waiting on a round of fixes to land in a patch release branch. I should know more later today about specifically which release they will land in. I’ll update this thread with that information.
Sorry for the delay in my response. We had some trouble getting these changes through the release pipeline. They should be available in the 2017.1.1p2 patch release.
Just to confirm - this was fixed in today’s patch, right?
The commit references “case 926881”, and there’s a fix for 926881 in the patch notes, but the patch note text is: “Scripting Upgrade: Fixed a crash when inspecting values in managed debugger”. I’m guessing those are the same issue, but I wanted to make sure before forcing a project upgrade for the entire office.
Yes, that is the same issue. I would recommend trying it (and most patch releases) at a smaller sope locally to ensure they correct the bug before pushing it out, if possible though. This crash happened often, but it was still intermittent. We may not have caught all of its causes.
We’ve been on 2017.1.1p2 for a while, and the crash frequency haven’t seemed to change much. I just updated to 2017.2, and it’s still crashing quite a bit.
I posted a bug report (960586) containing the crash dump and log, in case that might help.
Hello!
We have a similar problem in the project…
I practically collected a minimal project with the reproduction of frequent crashes, but it still has a third-party asset…
Soon, if I manage to get rid of it, I’ll try to send a bug report.
This is a very complex mistake and it is difficult to find a regularity for sustainable reproduction.
I even had to write a special test script that constantly start and stop the Play mode to speed up the search for the patterns of crash.
Here’s how it looks Unity 2017.2.0f3, Win 7x64, Net 4.6:
Has managed to issue the minimum test project: https://github.com/CriDos/UnityTestBug
Confirmed in Unity 2017.2.0f3 and 2017.3.0b9.
Later I will try to issue a bug report, now it’s too late…
I also have frequent crashes when using 4.6. The QA team said they could confirm it was caused by 4.6, but they eventually gave up and told me to try latest beta. I’ve gone through QA on this with several versions now of unity now and each time they tell me to try latest beta after giving up, and they if they don’t hear from me again they’ll assume it’s all good haha.
Well, I switched back to the old run-time in the end. I was unable to determine the cause of the crashes, and QA team are probably pretending there’s no problem again lol.
Good luck though, really hoping 4.6 becomes stable…
Can you send me (here or privately) the bug report numbers for these issues? Sometimes our QA is a little too aggressive in resolving issues like this. I’d like to take a look at the crash reports to see if we can find the cause. Thanks!
