Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X
Votes
0
Found in
2021.3.29f1
2022.3.9f1
2023.1.9f1
2023.2.0b9
2023.3.0a5
Issue ID
UUM-49019
Regression
No
The Profiler shows incorrect data and spams the console with "Missing Profiler.EndSample" errors when there is an Input System Component in Scene and switching to profiling in Deep Mode
How to reproduce:
1. Open any project with the Input System installed
2. Import the attached Unity Package
3. Open Scene "ConnectedSystems"
4. Navigate to Window > Analysis > Profiler
5. Enter Play Mode and see that the Profiler is recording
6. Switch to "Deep Profile" in the Profiler
Expected result: The Profiler continues recording with Deep Profiling enabled without errors thrown and the visual data does not change
Actual result: The Profiler floods the console with the error "Missing Profiler.EndSample" and visual data changes
Reproducible with: 2021.3.29f1, 2022.3.9f1, 2023.1.9f1, 2023.2.0b9, 2023.3.0a5
Note: Deep Profiling is virtually impossible in this state with Input Systems Components
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Add comment