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
-
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
This is a duplicate of issue #951953