Search Issue Tracker

Fixed in 2017.2.0f3

Fixed in 2017.1.X



Found in


Issue ID




[Windows][Standalone] Crash when exiting standalone 'UnityPlayer.dll caused an Access Violation'



How to reproduce:
1. Open attached project
2. Build windows standalone
3. Start the build
4. Once it's running, exit the build by ALT+F4 or other means
-- Standalone crashes

Reproduced on: 2017.2.0b5, 2017.2.0b7, 2017.2.0b8
Not reproduced on: 2017.2.0b4, 2017.3.0a1, 2017.3.0a4
Regression introduced in: 2017.2.0b5

Comments (6)

  1. David-J-Foster

    Aug 01, 2018 17:34

    This _really_ needs to be fixed in 2017.4.8f1. What is the point of a "Long Term Support" version that will have had 3+ months of support and bug fixes but yet hasn't recieved a fix for severity #1 bug like this one?

    Right now, I cannot ship my game to Oculus because it will fail their technical review. One requirement is that, when apps exit, they return an exit code of 0 so that the Oculus runtime knows the app exited properly. If this bug occurs (and it does 25-33.3% of the time, by my testing), the exit code won't be returned and I will fail technical review.

    Unity, PLEASE fix this in 2017.4. It is absolutely critical!

  2. DavidLewis

    Jun 05, 2018 21:00

    Aragami [version: Unity 2017.2.1p2 (1dc514532f08)]

    UnityPlayer.dll caused an Access Violation (0xc0000005)
    in module UnityPlayer.dll at 0033:27472d23.
    Error occurred at 2018-06-05_214142.

  3. BigScaryBoo

    Feb 13, 2018 12:33

    Still happens on Unity 2017.2f1 with .NET 3.5 (API compatibility .NET 2.0 Subset)

  4. hepphep

    Feb 02, 2018 07:35

    Can confirm that this still happens in Unity 2017.3f3 when using .Net 4.6 Scripting runtime, except it is not always crash but can also be very long unresponsive freeze (like five minutes or so) after which it gets closed.

  5. aaron_cowie_cruiser

    Jan 18, 2018 07:32

    Still happens in Unity 2017.3 when using .Net 4.6 Scripting Runtime

  6. ChaosHelme

    Oct 14, 2017 14:53

    This still happens in Unity 2017.2 when using .Net 4.6 Scripting Runtime

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.