Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.5.X, 5.6.X, 2017.1.X
Votes
0
Found in
5.6.1f1
Issue ID
914366
Regression
No
Crash report is not generated when Standalone build crashes in Program Files
Steps to reproduce:
1. Open Unity as an administrator
2. Open the attached project (CrashTest.zip)
3. Open the CrashTest scene
4. Build into the Program Files folder
5. Close Unity
6. Run the build
7. Click on the "Crash me" button
8. Observe, a dump file is not generated
Expected result: Unity should generate a crash report
Actual result: Unity does not generate a crash report
Reproduced with: 5.4.5p2, 5.5.3p4, 5.6.1p1, 2017.1.0b7
Fixed in:
2017.2.0b5
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
Add comment