Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.3.0b1
Issue ID
951953
Regression
Yes
Windows Standalone 64-bit Build Crashes on launch
Reproduction steps:
1. Create a new project
2. Build for Windows (64-bit)
3. Launch the Standalone Build
Expected Result: The Build launches
Actual Result: The Build crashes
Fixed in: 2017.3.0b3
Reproduced with: 2017.3.0b1
Regression introduced in: 2017.3.0b1
Did not reproduce on: 2017.3.0a7
Note:
Only Reproduces when building for Windows Standalone
Unhandled exception at 0x00007FFC01FB5905 (UnityPlayer.dll) in crash.dmp: 0xC0000005: Access violation reading location 0x0000000000000008.
Comments (17)
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
andrewweitzer
Feb 12, 2018 22:18
This is still an issue
2017.3.0f3
crash664
Feb 02, 2018 04:10
Issue still up for me too! 2017.3.0f3
TripleMotionMedia
Jan 22, 2018 11:06
Issue still up ! 2017.3.0f3
JoelPlourde1
Jan 19, 2018 19:40
Issue still up ! 2017.3.0f3
SgtOkiDoki
Jan 15, 2018 14:39
This issue is still up!
2017.3.0f3
BenouKat
Oct 30, 2017 14:20
Are you sure this is not a bug from 2017.2 ? Because something similar happened to my client on this version.
XXXXXXXX [version: Unity 2017.2.0f3 (46dda1414e51)]
UnityPlayer.dll caused an Access Violation (0xc0000005)
in module UnityPlayer.dll at 0033:e2110ce7.
Read from location 00000038 caused an access violation.