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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #951953