Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
19
Found in
2020.1
2020.1.14f1
2020.2
Issue ID
1295472
Regression
No
AsyncGPUReadback.RequestIntoNativeArray causes InvalidOperationException on NativeArray
How to reproduce:
1. Open the attached project named "Case_129547"
2. Open the TestScene2 in the Scenes folder
3. Enter Play mode
4. Observe the Console Window
Expected result: No errors are thrown on entering the Play mode
Actual result: InvalidOperationException on NativeArray error is thrown
Reproducible with: 2020.1.17f1, 2020.2.1f1, 2021.1.0a10
Could not test with: 2018.4.30f1, 2019.4.17f1(Missing script references)
Reproducible with graphics APIs: D3D11, D3D12, Vulkan, OpenGLCore
Notes:
1. Does not reproduce on all machines
Comments (16)
-
Drumsmasher17
Dec 14, 2024 22:13
Am getting this error on Unity 6000.0.19f1
InvalidOperationException: The Unity.Collections.NativeArray`1[GPUDecalUtils+ReadableVertex] can no longer be accessed, since its owner has been invalidated. You can simply Dispose() the container and create a new one.
Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle.CheckWriteAndThrowNoEarlyOut (Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle handle) (at <c01ea92c157f4fadb827b390bd34dd65>:0)
Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle.CheckWriteAndThrow (Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle handle) (at <c01ea92c157f4fadb827b390bd34dd65>:0)
Unity.Collections.LowLevel.Unsafe.NativeArrayUnsafeUtility.GetUnsafePtr[T] (Unity.Collections.NativeArray`1[T] nativeArray) (at <c01ea92c157f4fadb827b390bd34dd65>:0)
UnityEngine.Rendering.AsyncRequestNativeArrayData.CreateAndCheckAccess[T] (Unity.Collections.NativeArray`1[T] array) (at <c01ea92c157f4fadb827b390bd34dd65>:0)
UnityEngine.Rendering.CommandBuffer.RequestAsyncReadbackIntoNativeArray[T] (Unity.Collections.NativeArray`1[T]& output, UnityEngine.ComputeBuffer src, System.Action`1[T] callback) (at <c01ea92c157f4fadb827b390bd34dd65>:0) -
thebarryman
Sep 13, 2023 02:20
Still appears to be broken.
-
nicbarkeragain
May 11, 2023 03:25
This is still happening when trying to read a rendertexture to a nativearray in 2021.3.15f1.
-
gregoire_unity128
Jun 07, 2022 15:29
I just encountered this issue, too. On 2022.1.3f1. lots of trouble for array copy, guys...
-
LooperVFX
Oct 09, 2021 01:54
"Hi all, the fix has finally landed in 2022.1.0a12.
This means the backports will now be unblocked and can land in the main releases."
- richardkettlewell @ Unity Technologies, Monday October 4th 2021 -
wusticality
Sep 01, 2021 21:31
Is there any update on this? The status hasn't changed since May.
-
qijen
Aug 18, 2021 04:29
Need to be fixed on 2019.4.
-
iamarugin
Aug 06, 2021 08:44
2020.3 when?
-
unity_nDI54UEnEZerWg
Aug 01, 2021 10:47
Request to fix this issue on 2020.3.X.
-
miknios
May 29, 2021 07:56
Please fix :)
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a12
Resolution Note (fix version 2021.2):
Fixed in Unity 2021.2.2f1
Resolution Note (fix version 2020.3):
Fixed in - 2020.3.23f1