Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
1
Found in
2020.3.47f1
2021.3.23f1
2022.3.29f1
2023.2.0a11
6000.0.0b11
Issue ID
UUM-33315
Regression
No
[URP] Errors regarding Profilers.EndSample thrown while recording profiling information with Profiler when using custom ScriptableRenderPass with URP
How to reproduce:
1. Open the “profiler_errors_repo.zip“ project
2. Open the “SampleScene“ scene
3. Open the Profiler by going to Window -> Analysis -> Profiler
4. Set the Profiler to “Edit Mode“
5. Start recording profiling information
6. Observe the Console
7. Set the Profiler to “Play Mode“
8. Clear the Console
9. Enter Play mode
10. Start recording profiling information
11. Observe the console
Expected result: No Profiler errors were observed when Profiler starts recording in “Edit Mode“ and “Play Mode“
Actual result: Errors regarding Profilers.EndSample were observed when Profiler starts recording in “Edit Mode“ and “Play Mode“
Reproducible with: 2020.3.47f1, 2021.3.23f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11
Reproducible 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
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
- The cogwheel button in the Build History window gets distorted when the Build History window is resized or options are ticked in the toolbar
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (6000.0.X):
There are no fixes planned for this Bug