Search Issue Tracker

Fixed in 2021.1

Fix In Review for 2019.4, 2020.1

Fixed in 2020.2

Votes

0

Found in

2019.4

2020.1

2020.1.1f1

2020.2

Issue ID

1271254

Regression

No

[IL2CPP] UnsafeUtility methods generate garbage when using IL2CPP Scripting Backend

IL2CPP

-

How to reproduce:
1. Open the attached "1271254 repro" project
2. Open Build Settings and make sure that Development Build and Autoconnect Profiler options are checked
3. Build and Run the project
4. Open the Profiler window from Window > Analysis > Profiler
5. Open the Memory Module of the Profiler window

Expected results: UnsafeUtility doesn't generate garbage regardless of the Scripting Backend
Actual results: UnsafeUtility generates garbage when using IL2CPP

Reproducible with: 2019.3.0f1, 2019.4.8f1, 2020.1.0a1, 2020.1.3f1, 2020.2.0a21
Could not test with: 2018.4.26f1 (certain UnsafeUtility methods aren't available), 2019.3.0b12 and earlier (required versions of Collections package aren't available)

Notes:
-The memory spikes in the profiler are around 36kB in size when using IL2CPP
-Switching Scripting Backend to Mono makes the issue disappear completely without tiniest memory spikes

  1. Response avatar

    Resolution Note (fix version 2021.1):

    Fixed in 2021.1.0a1

  2. Response avatar

    Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0b7

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.