Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.0a16
Issue ID
UUM-7825
Regression
No
"Non-matching Profiler.EndSamplelogged" error appears when recording a Windows 32-Bit Player
Reproduction steps:
1. Create a new Unity project
2. Go to File > Build Settings
3. Set Architecture to "Intel 32-bit"
4. Check the "Development Build" checkbox
5. Build and Run
6. Go to Window > Analysis > Profiler
7. Connect the Profiler to the Windows Player
8. Record profiling information and observe the Console
Expected result: There are no errors
Actual result: Non-matching Profiler.EndSample errors are thrown
Reproducible with: 2020.3.36f1, 2022.2.0a16, 2023.2.0a19
Not reproducible with: 2021.3.6f1, 2022.1.7f1, 2023.1.0a2
Reproducible with: Windows 10 (on Mac using Boot Camp) and Windows 10 (PC)
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:
This issue only looks to occur on development 32bit players and is hard to reproduce. As 32bit development player is not a primary use case we will therefore look to close this bug.
Resolution Note (2022.2.X):
This issue only looks to occur on development 32bit players and is hard to reproduce. As 32bit development player is not a primary use case we will therefore look to close this bug.