Search Issue Tracker
Duplicate
Votes
0
Found in
5.1.0b5
Issue ID
694332
Regression
No
Crash on exit for Windows 64-bit Standalone players
64-bit Windows players built with Unity 5.1 beta 5 on Windows 7, Windows 8.1, or MacOS 10.10.3 crash when you close the player. 32-bit versions of these Windows players built on the same computers with the same versions of the Unity Editor do not crash upon exit.
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
cgonzalez509
Sep 11, 2015 10:52
Actually, the X64 crash happens on a Windows 8.1 machine, but it is working fine on a W7 one, so this problems suits better on the issue (http://issuetracker.unity3d.com/issues/untiy-64bit-5-dot-1-1f1-crashing-on-windows-8-dot-1)
cgonzalez509
Sep 09, 2015 10:28
Same happens to me. The stand alone exec is loading (both via DLLImport and LoadLibrary) an unmanaged C++ library.
- In the x64 version after closing the window and everything has been disposed that program crashes.
- In the x32 version, everything runs ok