Search Issue Tracker
Fixed
Fixed in 6000.2.7f1, 6000.3.0b4, 6000.4.0a2
Votes
0
Found in
2022.3.64f1
6000.0.53f1
6000.1.11f1
6000.2.0b9
6000.3.0a1
6000.4.0a1
Issue ID
UUM-110981
Regression
Yes
Crash on Texture2D:SetPixelImpl when rapidly calling Texture2D.Apply()
Reproduction steps:
1. Open the attached “IN-102738.zip” project
2. Open the “SampleScene”
3. Enter Play Mode
4. Wait for ~2-5 minutes
5. Observe the crash
Reproducible in: 2022.2.0a1, 2022.3.64f1, 6000.0.52f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Not reproducible in: 2022.1.0a1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Note: Crash does not occur on D3D11 or Vulkan
First few lines of stacktrace:
{noformat}
UnityEngine.Texture2D:SetPixelImpl_Injected <0x000f3>
UnityEngine.Texture2D:SetPixelImpl <0x00142>
UnityEngine.Texture2D:SetPixel <0x001ca>{noformat}
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
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
- Scene View Camera overlay preview goes out of Scene View bounds when the Scene View is resized vertically
- UI GameObjects are not positioned at 0,0,0 when creating them while Scene view is active
- Mesh Filter and Mesh Renderer property icons are difficult to see on blue highlight when selected in Animator window
Resolution Note (fix version 6000.4.0a2):
Thank you for reporting a bug to Unity.
Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.
Resolution Note (fix version 6000.3.0b4):
Thank you for reporting a bug to Unity.
Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.
Resolution Note (fix version 6000.2.7f1):
Thank you for reporting a bug to Unity.
Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.