2020.2.6 Access Violation in GameAssembly.dll on Player start: function-name not available (Win, IL2

Hello,

I would post an IssueTracker issue but I didn’t find how to create one.

I attach the crash dump and logs.

Even if you cannot debug this or don’t have time, perhaps you can give me a hint into the direction I can look to fix this or workaround this on my own.

This is a project which has been released for 3 years. It last worked good in Unity 2020.1 from before 8/8/2020. It still works good in Editor. I changed the Valve npm XR plugin to Unitys built-in Oculus and WMR because Valves is deprecated. “Nothing else” has changed except 3 plugins whose version bumped a place in the third position and those are 2 shader plugins and a runtime file picker.

@Tautvydas-Zilys apologies for directly referencing you. This issue has a similar wording like Unity 2018.2.7f1 Windows standalone crash on first run - UnityPlayer.dll caused an Access Violation - Unity Forum which you helped on.

The crash has always occurred directly after the Unity Intro when the scene is supposed to show. It’s on Windows with IL2CPP.

6890651–805787–Crash_2021-03-01_174818138.zip (40.6 KB)

See How to Report Bugs.

Looks like the crash is happening somewhere in Unity.Scenes.dll, which is part of the Entities package I believe.

Thank you for the link!

I will try to remove or update / downgrade the entities package. I think i have reworked my code back from entities where I tried to use them 2 or 3 years ago, last year.

Thank you very much!

It wasn’t Entities but one of the following:

Burst
Jobs
Post Processing
Visual Studio Code Editor

or one of the following I don’t see listed anymore under Unity Registry despite Preview Packages being enabled:

Mathematics
Unity Physics
Collections
Hybrid Renderer

I removed them, rebuild and now the Player plays :slight_smile:

Would you like me to report some sort of official bug report @Tautvydas-Zilys ? I have now a project which produces a non-crashing application but I made a backup of the project which produced the crashing application before.

Given the shared project is non-public (and obviously you don’t take the licensed assets in it) I can share it with you.

Thank you very much again! :slight_smile: