Search Issue Tracker

Won't Fix

Won't Fix in 6000.0.X

Votes

0

Found in

2020.3.39f1

2023.2.0a1

2023.3.0a3

6000.0.0b11

Issue ID

UUM-13586

Regression

No

CPU usage time for the CullScriptable method is ~1 ms per 200 portals when a specific project is built

Culling

-

How to reproduce:
1. Open the attached “1334716” project
2. Build And Run the project Scenes on Android with the “Development Build” flag set
3. Connect the device to the Profiler
4. Search and observe the “CullScriptable” CPU usage time

Expected result: CullScriptable CPU usage time is ~0.5 ms
Actual result: CullScriptable CPU usage time is 1-2 ms

Reproducible with: 2020.3.39f1
Couldn’t test with: 2021.3.9f1, 2022.1.16f1, 2022.2.0b7, 2023.1.0a9 (project isn’t compatible)

Reproduced on: macOS 12.5 (Intel)

Reproducible with devices:
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00331 - HUAWEI P20 lite (ANE-LX1), CPU: HiSilicon Kirin 659, GPU: Mali-T830, OS: 9
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
VLNQA00268 - Samsung Galaxy S10+ (SM-G975F), CPU: Exynos 9 9820, GPU: Mali-G76, OS: 10.0.0
(user’s info) - Samsung Galaxy S8
(user’s info) - Samsung Galaxy S20 5G

Note: The project attached to this issue is a minimal one with 250 portals. In the user’s project with 1000 portals up to 10-15 ms time usage is observed

  1. Resolution Note:

    Closing this issue as it have been solve.

  2. Resolution Note (6000.0.X):

    Closing this issue as it have been solve.

Log in to vote on this issue

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.

Latest issues

See all new issues