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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Add comment