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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment