Search Issue Tracker
Fixed
Fixed in 2020.3.46f1
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-2219
Regression
Yes
[Backport] Resources.Load triggers a continuation of a coroutine sending out a WebRequest if they are both executed in the same frame
Steps to reproduce:
1. Open the attached project ("1332433.zip")
2. Open "SampleScene"
3. Enter Play mode and notice that that you get 1, 2, 3, 4, 5 sequence in console
4. Build and deploy "SampleScene" to a device
5. Notice that the sequence produced is now 1, 2, 3, 5, 4
Expected results: Sequences match in editor and build (coroutine continuations are not triggered)
Actual results: Sequences do not match in editor and build (Resources.Load triggers a continuation of another coroutine that should only trigger in the next frame)
Reproducible with: 2019.4.25f1, 2020.3.8f1, 2021.1.6f1, 2021.2.0a11
Not reproducible with: 2018.4.33f1, 2021.2.0a12, 2021.2.0a17
Reproducible with:
Mac Standalone
iPad 9.7" 6th gen (14.4)
iPad Air 2 (11.0.3)
iPhone XR (13.4.1)
iPhone 8 Plus (14.4.2)
VLNQA00317, Vivo V1924A (V1924A), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00335, Samsung Galaxy S20 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00294, Oppo Reno Z 中国版 (PCDM10), Android 9, CPU: Mediatek MT6779 Helio P90, GPU: PowerVR Rogue GM9446
Not reproducible with:
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
Notes:
- Not reproducible in editor
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2020.3.46f1):
Fixed in: 2020.3.46f1