Search Issue Tracker
Fixed in 2023.1.0b16
Fixed in 2023.1.X, 2023.2.X, 2023.2.0a12
Votes
0
Found in
2023.1.0b5
2023.2.0a1
Issue ID
UUM-30279
Regression
Yes
Crash on ExrDecoder::DecodePixelsImpl when loading .exr texture file
Reproduction steps:
1. Open the attached project “CrashRepro“
2. Click on Bug>LoadImageEXR
Expected result: Texture gets loaded
Actual result: Editor crashes
Reproducible with: 2023.1.0a11, 2023.1.0b5, 2023.2.0a1
Not reproducible with: 2020.3.45f1, 2021.3.191f, 2022.2.7f1, 2023.1.0a10
Couldn’t test with: 2023.2.0a4 ({{Missing default layout}} table shows up when opening project and reverting to factory settings shows the same table)
Reproducible on: Windows 10
First few lines of stack trace:
{noformat}0x00007FFC19F17329 (Unity) ExrDecoder::DecodePixelsImpl
0x00007FFC19F0FFB7 (Unity) LoadImageIntoTextureImpl<ExrDecoder>
0x00007FFC19F19BFC (Unity) LoadMemoryBufferIntoTextureInternal
0x00007FFC19F197B7 (Unity) LoadMemoryBufferIntoTexture
0x00007FFC19F20DAC (Unity) ImageConversionBindings::LoadImage
0x00007FFC18C68993 (Unity) ImageConversion_CUSTOM_LoadImage_Injected{noformat}
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 ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment