Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.0b2
Issue ID
955646
Regression
Yes
[Windows] [2017.3] UnityPlayer.dll causes Access Violation when running x86_64 built scene
To reproduce:
1. Create a new project
2. Build and run
Expected: scene will run without any errors
Actual: 'UnityPlayer.dll caused Access Violation (0x0000005)' is thrown
Reproducible: 2017.3.0b1, 2017.3.0b2
Not reproducible: any 5.6, 2017.1, 2017.2, 2017.3.0a1, 2017.3.0a7
Comments (1)
-
antpb
Apr 09, 2018 21:57
I am still seeing this. Build breaks on anything done in 2017.2 and above. 2017.1 works fine.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #951953