Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2020.3.X, 2021.2.X



Found in




Issue ID




AsyncGPUReadback.RequestIntoNativeArray causes InvalidOperationException on NativeArray

Visual Effects


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

1. Does not reproduce on all machines

  1. Response avatar

    Resolution Note (fix version 2022.1):

    Fixed in: 2022.1.0a12

  2. Response avatar

    Resolution Note (fix version 2021.2):

    Fixed in Unity 2021.2.2f1

  3. Response avatar

    Resolution Note (fix version 2020.3):

    Fixed in - 2020.3.23f1

Comments (12)

  1. F6f8e787dd99d5a64210b32c7ef25d25?d=mm


    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

  2. Acf31814caa6cacf162bd683ca2af38c?d=mm


    Sep 01, 2021 21:31

    Is there any update on this? The status hasn't changed since May.

  3. C8663853e70c7179589f63d90db9285d?d=mm


    Aug 18, 2021 04:29

    Need to be fixed on 2019.4.

  4. 64997828c7bb6a64e0f8a050a5963125?d=mm


    Aug 06, 2021 08:44

    2020.3 when?

  5. 8187349b524496fdf69590c12eee9652?d=mm


    Aug 01, 2021 10:47

    Request to fix this issue on 2020.3.X.

  6. Ea00d9cf3130735630d3ac0e021e9a63?d=mm


    May 29, 2021 07:56

    Please fix :)

  7. F6f8e787dd99d5a64210b32c7ef25d25?d=mm


    May 18, 2021 20:27

    @wojimus this bug has been known since 2020, not 2015. AsyncGPUReadback wasn't a class in Unity until 2018 and RequestIntoNativeArray wasn't a method until 2019. It's impossible for a feature to have bugs before it even existed.

    In any case, we can see on the issue tracker here the "Fix is in Review" meaning a fix has already been made internally, and is almost ready to release publicly. It's just going through a quality testing process. more info here:

  8. 6d82b8b913e5f7f8d401825d84161c9f?d=mm


    May 15, 2021 05:17

    This bug is still here and It's been known since 2015, come on guys,

  9. Acf31814caa6cacf162bd683ca2af38c?d=mm


    May 11, 2021 09:03

    What is the status of this?

  10. E3dbfd4ea21d14dc939db9b6ffc3e465?d=mm


    Mar 25, 2021 02:50

    Encountered on 2019.4 too.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.