Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.1f1
Issue ID
959234
Regression
No
Editor Crash in Imf_2_2::copyIntoFrameBuffer when Importing .exr texture
To reproduce:
1. Create and open new Unity project.
2. Download and import .exr texture into Unity from provided link.
Expected result: .exr asset is imported into Unity.
Actual result: Unity freezes on Windows machine. Unity crashes on Mac Machine. Asset fails to import.
Reproduced with: 2018.1.0a1, 2017.3.0b5, 2017.2.0f3, 2017.1.1p2, 2017.1.0b1.
Notes: Before 2017.1.0b1 Unity stops crashing due to the fact that .exr texture is not recognized with "Could not create texture from Assets/case_959234-pano_4K_COMP_FINAL_v002.exr: File could not be read" error.
Verified with 2018.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment