Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.36f1
Issue ID
UUM-4739
Regression
Yes
"Assertion failed on expression: '(*v & 0xFF) > 0'" thrown in the Console window when press the "Record" button in Profiler (Standalone Process"
How to reproduce:
1. Create a new empty project
2. Open the Profiler Window Standalone (Window -> Analysis -> Profiler (Standalone Process))
3. Make sure that Profiler's Target Selection is set to "Play Mode"
4. Enter the Play mode in the Editor
5. Go back to the Profiler and press the "Record" button (might need to press the "Record" button multiple times for an error to appear)
6. Observe the errors that appear in the Console window in the Editor
Expected result: No errors are thrown in the Console window when pressing the "Record" button
Actual result: "Assertion failed on expression: '(*v & 0xFF) > 0'" error is thrown in the Console window when pressing the "Record" button
Reproducible with: 2020.3.36f1
Not reproducible with: 2020.3.35f1, 2021.3.4f1, 2022.1.5f1, 2022.2.0a16
Could not test with: 2019.4.39f1 (Profiler (Standalone Process) is not introduced)
Reproduced on: Windows 10
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The issue happens in only legacy LTS. Unlikely to be prioritized due to low impact
Resolution Note (2020.3.X):
The issue happens in only legacy LTS. Unlikely to be prioritized due to low impact