Search Issue Tracker
In Progress
Fix In Review for 6000.3.X, 6000.4.X
Votes
0
Found in
6000.3.0b1
6000.4.0a1
Issue ID
UUM-117133
Regression
Yes
Switching Platform while profiling in Edit Mode throws “Non-matching Profiler.EndSample” warnings
Steps to reproduce:
1. Create new Unity project
2. Go to Window > Analysis > Profiler
3. Change profiling mode to Edit mode and let it profile
4. Open Build Profiles window
5. While profiling, switch to iOS Profile
6. Observe the errors thrown in the Console window
Actual results: multiple “Non-matching Profiler.EndSample” errors are thrown in the Console after switching Platform while profiling in Edit Mode
Expected results: No errors should be thrown in the Console, profiler should stop profiling when switching to different platform
Reproducible with versions: 6000.3.0a1 (4592b02ab560), 6000.3.0b1
Not reproducible with versions: 6000.2.4f1 (17550c9bb584)
Tested on (OS): Windows 11, macOS Silicon, Sequoia 15.6 (M1)
Notes:
- Does not reproduce in Play Mode
{code:java}
Non-matching Profiler.EndSample (Every EndSample call must have a preceding BeginSample call within the same frame): UIElementsUtility.DoDispatch(Non Repaint Event)
Previous 5 samples:
Mono.JIT
GC.Alloc
UIElements.PickAll
UIElements.UpdateElementBounds
UIElements.UpdateLayout
In the scope:
EditorLoop
Main Thread
{code}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment