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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Add comment