Mono Upgrade Frequent crashes

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 can send crash dumps or whatever, if it helps.

 

Any updates?

 

Is "soon" going to be p6? If that's not the case, is there any way for me to compile the Mono version myself and replace the one used by Unity?

Whatever I'm working on right now seems to trigger this a lot, and restarting the editor every 15-20 minutes due to crashes breaks my flow somewhat.

 

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.

 

Hi!

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.

 

Nope! The project is VC'd through git, but we do that in an external application.

 

As in Task? Nope, none.

 

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...

 

Sent editor bug report: (Case 968421) Frequent crashes when playing mode starts after passing to .NET 4.6
The memory dump will be later..

Sorry, I accidentally duplicated the bug report (Case 968422)

 

Added: https://issuetracker.unity3d.com/is...ering-slash-leaving-play-mode-on-mono-4-dot-6
But judging from the priority, the bug is underestimated

 

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...

 

No problem. It's case number 970413.
I'll try again with 2017.3 when released, but for now I'm fine working with the old run time.
Cheers.

 

QA got back to me, and apparently the crashes I'm experiencing is from this bug.

Any clue how far away "Fixed in future release" is?

 

Thanks for the info!

 

I am having semi-random crashes as well but I am not sure where to report them since they are related to the debugger.

The combination of:
- debugger attached
- changing files in VS and switching to Unity (so it recompiles)
- previously having done debugging (single-stepping etc)

Often results in Unity crashing for me.
Either at the part where it recompiles, or when I enter or exit play mode.

The only way I have never gotten a crash so far is:
- when in vs detach the debugger
- only ever attach when unity has fully recompiled, and is not in play mode


The crashes never show the unity bug reporter tool. Its always the "program is not responding" thing.
How do I report that?
And to whom?
Do you guys handle this stuff or should I rather inform the VSTU team (and if so, how?)

I'm using 2017.3.0f2 + latest VS version.

 

Any clues on when this fix will land in 2017.3? It's not in the patch notes for either the full .3 release or for p1.

 

Gotta say I'm a bit disappointed with the progress on this. Editor crash bugs are quite serious - I'm losing a lot of time to having to restart Unity again and again. Having a turn around of month between having a fix ready, and getting the fix into the engine is understandable for something minor, but I'd hoped to see something more rapid for crashes.


The amount of crashes also seems to have increased from 2017.2 to 2017.3. There's probably something else going on, but I can't report anything because I'm waiting for the fix to the known crash bug.

Do you have any internal 2017.3 version with the fix in that you could share? Then I could figure out if the crashes are actually fixed, or if there's other issues, so you don't have to wait until the 10th to get reports for that.

 

Windows 10 64 bit.

 

joncham, I have no crashes with the new Mono library!
For several days I worked with her in Unity 2017.3.0p1 Windows 7x64...

 

I've got no crashes for two days, so it seems like the mono version fixes things. Thanks!

 

Also tried the new dll and have had no crashes for almost three days. Before that it was about 20 crashes per day. So, seems to work like a charm.