Search Issue Tracker
In Progress
In Progress in 6000.6.X
Votes
2
Found in
6000.3.10f1
6000.4.0b10
6000.5.0a7
6000.6.0a1
Issue ID
UUM-135024
Regression
Yes
Crash on TexturesD3D12::CreateTextureInternal() when opening a project for the first time
How to reproduce:
1. Open the attached “IN-131773” project
2. Observe the crash
Reproducible with: 6000.2.0a10, 6000.3.10f1, 6000.4.0b10, 6000.5.0a7
Not reproducible with: 6000.0.68f1, 6000.2.0a9
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- The crash only reproduces on a freshly extracted project
- The crash does not occur when using DX11 or Vulkan
First few lines of the stack trace:
0x00007FFC417C7186 (Unity) LaunchBugReporter
0x00007FFC41932BAF (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFC419336D0 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFC408F3F7D (Unity) DebugStringToFilePostprocessedStacktrace
0x00007FFC408F32F9 (Unity) DebugStringToFile
0x00007FFC40A061CA (Unity) CheckDeviceStatus
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment