Search Issue Tracker

Active

Under Consideration for 6000.5.X

Votes

0

Found in

6000.0.67f1

6000.3.7f1

6000.4.0b7

6000.5.0a6

Issue ID

UUM-133765

Regression

No

Profiler search results are delayed when any search result is selected, and another frame is viewed

Profiling

-

How to reproduce:

  1. Open the “IN-133270.zip“ project
  2. Open the “SampleScene“
  3. Open “Window → Analysis → Profiler“
  4. Enable recording in the Profiler
  5. Enter Play Mode
  6. Select any frame in the CPU Usage in the Profiler
  7. Search for “Destroy“ in the lower section of the Profiler
  8. Select any result
  9. Select any other frame in the CPU Usage in the Profiler to view its search results
  10. Observe the time taken for the search results to show up

Actual result: Search results are shown with a long delay (~300ms)
Expected result: Search results are shown immediately

Reproducible in: 2023.1.0a1, 6000.0.67f1, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6

Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested

Notes:
- Reproducible with any result that is not at the top of the hierarchy (for example, selecting “PlayerLoop“ will not reproduce, but selecting any result under it will reproduce)
- Not reproducible if no search result is selected
- Not reproducible if any profiler result is selected, but nothing is searched
- Only “Timeline” is not affected, but “Hierarchy”, “Raw Hierarchy“, and “Inverted Hierarchy“ are affected

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.