Search Issue Tracker
Won't Fix
Votes
2
Found in
2022.3.51f1
6000.0.24f1
6000.1.0a1
6000.2.0a1
7000.0.0a1
Issue ID
UUM-85584
Regression
No
Editor crashes on GfxDeviceD3D12::UploadTextureSubData2DImpl when opening the Scene view
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Samples/Meta Movement/69.0.0/Body Tracking Samples/Scenes/MovementHighFidelity.unity” Scene
3. Open Scene view
Expected result: Editor does not crash and continues to run
Actual result: Editor crashes
Reproducible with: 2022.2.5f1, 2022.3.51f1, 6000.0.24f1, 6000.1.0a1
Not reproducible with: 2021.3.45f1
Could not test with: 2022.1.24f1, 2022.2.0a19, 2022.2.0b16, 2022.2.4f1 (Library\PackageCache\com.meta.xr.sdk.interaction@69.0.0\Editor\QuickActions\Scripts\TeleportWizard.cs(200,37): error CS0117: 'GameObject' does not contain a definition for 'FindAnyObjectByType')
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
First few lines of the Stacktrace:
0x00007FF69C571105 (Unity) GfxDeviceD3D12::UploadTextureSubData2DImpl
0x00007FF69C2F0F08 (Unity) GfxDevice::UploadTextureSubData2D
0x00007FF69DB52959 (Unity) GfxDeviceWorker::RunCommand
0x00007FF69DB5ABAB (Unity) GfxDeviceWorker::RunExt
0x00007FF69DB5ACC8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
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 ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Resolution Note:
There are no fixes planned for this Bug