Search Issue Tracker
Fixed in 2018.1.X
Won't Fix in 2017.1.X, 2017.4.X
Fixed in 2017.2.X
Votes
3
Found in
2017.1.2f1
Issue ID
957169
Regression
Yes
[Enlighten][Debug build] Player crashes with Heap corruption error at exit
Windows standalone x64 built with "Development Build" and "Script Debugging" options crashes on Build Exit.
Heap corruption error can also be observed when a player is built with debug version of Unity
Steps for reproduction:
1) Compile debug build of Unity
2) Create an empty scene with a cube
3) Ensure that Enlighten is selected as backend and realtime GI is enabled (default settings are used)
4) Deploy the Windows standalone build
5) Open the player (everything works as expected)
6) Exit the player by closing it
7) Observe the Heap Corruption error as shown on the image below
Fixed in: 2018.1.0a6
Expected Result: The Build Exits normally
Actual Result: the Build Freezes/Crashes
Reproduced with: 2018.1.0a1, 2017.3.0b4, 2017.2.0f3, 2017.1.2f1
Did not reproduce on: 5.6.4f1 (Script Errors)
Note:
2017.3.0b4 needs "AutoConnect Profiler" and you need to Click on the Button and Clear the Development Console before step 4
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