A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Discussion in 'Experimental Scripting Previews' started by Xarbrough, Aug 2, 2017.
@joncham are there any predictions when 4.6 will become stable and default option in Unity?
Just want to chime in here I am also experiencing very regular crashes when using .Net 4.6 with Unity 2017.2.0f2 on Windows 10.
I thought it was the VS debugger causing issues at first but it seems to crash regularly even without the debugger. Seems to happen only on large project and crashes about one in every 4-5 plays.
2017.3.0p2 helped a lot for me, and the editor no longer crashes to desktop. The editor occasionaly freezes though, and I have to end the process in the task manager to close it.
If that problem is fixed I'll be happy with how the editor works on .NET 4.6.
Please try the latest 2017.3 patch release, if possible. I think we have corrected most of the problems.
When the editor freezes again, can you use Task Manager to generate a .dmp file from the Unity.exe process? Then please submit a bug report or send it to me privately on the forums. I'd like to know where the editor is hanging.
Thanks for replying. Sure! I'll try to do that today.
@JoshPeterson My editor froze again. I made a dump file of Unity.exe, but it's 0.7 gb zipped. How can I upload this?
The last output in Editor.log was:
[ 647 MB ]- Skipping packing - Sprite Packer (Legacy) is off.
[ 647 MB ]Reloading assemblies for play mode.
Begin MonoManager ReloadAssembly
This looks hung in domain reload. Likely a thread is stuck (IO, networking, native call) and we are waiting for it to exit.
Should I report av bug, and if so can I include the 0.7 gb dump file?
A 2017.3 patch release fixed this issue for me, but I can't find if that patch hit the 2018 beta, and when I tried beta 4 I started getting consistent crashing that looked like this issue. Dug through the beta release notes and couldn't find any references to the app domain loading fix.
Is there any info on if that fix is actually in 2018 yet, or if not when it might hit?
Unity Editor [version: Unity 2017.3.0f3_a9f86dcd79df]
unity caused an Access Violation (0xc0000005)
in module mono-2.0-bdwgc.dll at 0033:36e9fb36.
Error occurred at 2018-02-01_163000.
C:\Program Files\Unity\Editor\Unity.exe, run by Kophax.
22% memory in use.
32693 MB physical memory [25334 MB free].
37557 MB paging file [28809 MB free].
134217728 MB user address space [134214416 MB free].
Read from location 00000000 caused an access violation.
Also getting this every few minutes since upgrading project to 4.6.
It's a simple project right now with a new UI managing the hosting/joining servers. Basically I'm replacing NetworkManagerHUD with my own. It happens inconsistently on various UI interactions so it's leading me to believe it's not related to any specific UI/networking interaction specifically. The game is fine once built of course.
One thing to note when I switched this over is VS complained about the project being in a slightly different version (4.6.5 vs 4.6.1) or something like that. At first i tried installing the slightly different build number but that didn't seem to work, so I chose the default option (change project to use 4.6.1 i think) and everything seemed fine. Sorry this is vague as I can't seem to reproduce that warning, even if i delete my proj files.
Is the mono-2.0-bdwgc.dll library unity's interface to the .NET runtime or does the 2.0 potentially indicate something got missed along the way?
I've got a project here that can reproduce this within a minute of heavy testing almost every time if it would help.
Please try the latest 2017.3 patch release, available here:
The "2.0" in mono-2.0-bdwgc.dll is unrelate to the .NET profile version. It means version 2.0 of the Mono embedding API.
I think this fix is in 2018.1b1, so you might be seeing something subtly different. Can you submit a bug report when you see it again in 2018.1? Please let me know the bug number, and then I can easily track down the crash information to see if it is a similar issue or something new.
Bug report submitted 996932.
This exhibits the same behavior for me as the app domain reloading issue. Consistently 1 out of 3 times or so it crashes entering play from a specific UI heavy scene.
Note that I submitted it in 2017.3, but the included editor log is from 2018.1 beta 5 at the time of crash.
The scene is from a large project, but at the time it was very late and I didn't stop to think that I could probably export a unity package of that scene plus dependencies which as it turns out is only 17mb. It won't run like it does in my project being a multiplayer app and all, but if you think it might be useful let me know where to send it.
Thanks! We will let you know via the bug report if we need anything else.
After upgrading from 2017.3.0p2 to 2017.3.1f1 I haven't experienced any more freezes. It usually occurred when entering play mode, but I've done this at least 30 times without incident.
Just wandering, will .NET 4.6 still be tagged as experimental when 2018.1 is released?
Are there plans to make it stable?
We're working on making it stable now, but we don't have any plans to announce yet.
If I try to add the two preview packages (1) Incremental Compiler and (2) Entities, then I am unable top change a project to .NET4.x Equivalent without totally ruining the project. After it asks me to restart the editor, Unity crashes every time I try to open this project. Somehow, the NET.4.x and unity ECS packages conflict, which is especially annoying because lots of people on the forums were saying you need .NET.4.x to use ECS.
I'm on Unity 2018.2.3f for the Linux build. Sadly, neither ECS nor Unity.Mathematics are working for me, and all these problems seem to be intermingled in a way that I'm not able to solve it!!
Can you get to the bug reporter in the Unity Editor? We'd love a bug report with this project if possible. Also, do you have access to Windows or macOS to try on those platforms? I'd like to know if this is an issue specific to the Linux editor.
I sent a report now, using the new 2018.2.4f1 Linux build, and am just installing it on my Mac OSX to see if I get similar problems. Will update shortly.
I can't replicate the bug on my MacBook. Seems like a Linux thing I'm afraid :/
We received similar crash reports for the standalone player of our game using the latest LTS release (can't personally reproduce it).
Parkitect [version: Unity 2017.4.16f1 (7f7bdd1ef02b)]
mono-2.0-bdwgc.dll caused an Access Violation (0xc0000005)
in module mono-2.0-bdwgc.dll at 0033:e9f2780e.
Error occurred at 2018-12-05_214600.
C:\Program Files (x86)\Steam\steamapps\common\Parkitect\Parkitect.exe, run by Student.
58% memory in use.
4012 MB physical memory [1663 MB free].
7340 MB paging file [3968 MB free].
134217728 MB user address space [134213097 MB free].
Read from location 0000002a caused an access violation.
Is there anything we can do to help figure this out?
Are there any call stack details along with this crash report?
Ah, sorry! Attached are the crash dump files I received.
This looks like a pretty odd crash. It happens very early in the application startup process, in code that should run for every application. I've not seen this before. If you submit a bug report we might be able to associate this with other crash dumps that are similar, but at the moment, I don't understand the cause of this issue.
We has same crashes.
our server runs many instances of the application. they don't live very long. One server for one match. As a result in a few hours one or several of them will crash.
I just got the same issue. It seems to be related with "mono-2.0-bdwgc.dll caused an Access Violation" as well.
I attach my crash files. Thanks!
EDIT: In my case, it seems to be related with the 2DDL plugin (v1.4.0). Removing it from the project make my build run smooth again!
Hello, I have a crash in mono-2.0-bdwgc.dll when using Vegetation Studio Pro and trying to add in the DemoVegetationPackage biome. Usually, the editor just crashes silently with no logs, but I did get logs one time today when I was testing this.
Spoiler: Video demonstrating crash in mono-2.0-bdwgc.dll