Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.18f1
2022.2.5f1
2023.1.0b2
Issue ID
UUM-26176
Regression
Yes
Profiling builds created on older versions cause samples to be colored green when using a Profiler from newer versions
How to reproduce:
1. Create a new project
2. Open the Build Settings (File → Build Settings)
3. Turn on Development Build
4. Build And Run the project
5. Create a new project with a newer version than the previous project
6. Open the Profiler (Window → Analysis → Profiler)
7. Change the Profiling Target to the Build
Expected result: Different coloring for every type of running sample
Actual result: All running samples are colored green
Reproducible with: 2021.2.0a17, 2021.3.18f1, 2022.2.5f1, 2023.1.0b2
Not reproducible with: 2020.3.44f1, 2021.2.0a16
Reproduced on: macOS Ventura 13.1 (Intel), Windows 11
Notes:
- To reproduce the issue on 2020.3, a build was used from 2019.4
- Couldn’t test if the issue is reproducible when using older Editor versions to profile Builds from newer versions
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
- [Android][iOS] The keyboard closes and re-opens when consecutive input fields are selected
- Complex Sub Graph connected to a Voronoi node is ignored when the shader gets applied as a Material
- Compute Shader property not set error when entering play mode with path tracing and PBR sky
- "WebGL Publish" detects WebGL module and allows building when it is installed without restarting the project
- Editor is non-responsive and flickers when multiple Water System instances are enabled
Resolution Note:
This issue can only be reproduced by profiling a build created in Unity 2020 or older in an Editor version of 2021 or newer. Therefore because Unity 2020 is nearing end of life and we cannot land any changes to it, we will not be fixing this issue.